2 |
Approval of the agenda |
|
R4-2006000 |
Agenda for RAN4 #95-e |
RAN4 Chairman |
R4-2006001 |
RAN4#94-bis-e Meeting Report |
ETSI MCC |
R4-2008290 |
E-meeting arrangements and guidelines |
RAN4 Chairman |
3 |
Letters / reports from other groups / meetings |
|
R4-2006115 |
Over-the-Air Radiated Performance Testing for 5G mm-Wave (FR2) User |
5G Millimeter Wave Sub-Working Group |
R4-2006116 |
LS on requirement in Power Class 2 for UL MIMO Test cases |
GCF-CAG |
R4-2006117 |
LS on publication of TS.51 V1.0 |
GSM Association |
R4-2006118 |
Reply LS from CTIA CCLLC OTA WG to the GCF SG Concerning Antenna |
CTIA OTA Working Group |
R4-2006119 |
Reply LS on T_delta in IAB |
RAN1 |
R4-2006120 |
Reply LS on UE Tx switching period delay and DL interruption |
RAN1 |
R4-2006121 |
LS response on secondary DRX group |
RAN1 |
R4-2006122 |
LS on subcarrier spacing for CLI-RSSI measurement |
RAN1 |
R4-2006123 |
Reply LS on applicable timing for pathloss RS activated/updated by MAC-CE |
RAN1 |
R4-2006124 |
LS on removing the word |
RAN1 |
R4-2006125 |
LS on Signaling of Q Parameter for NR-U |
RAN1 |
R4-2006126 |
LS on Simultaneous reception of DL signals in intra-frequency DAPS HO |
RAN1 |
R4-2006127 |
LS on criterion of pathloss measurement failure for power control of SRS for positioning |
RAN1 |
R4-2006128 |
LS on updated Rel-16 RAN1 UE features lists for LTE |
RAN1 |
R4-2006129 |
LS on Rel-16 RAN1 UE features lists for NR |
RAN1 |
R4-2006130 |
Reply LS on UL LBT failure recovery for the target cell |
RAN2 |
R4-2006131 |
LS on UE specific DRX in NB-IoT |
RAN2 |
R4-2006132 |
Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
RAN2 |
R4-2006133 |
Reply LS on asymmetric channel bandwidths |
RAN2 |
R4-2008286 |
LS on positioning SRS during DRX inactive time |
RAN2 |
R4-2008287 |
LS on NeedForGap capability |
RAN2 |
R4-2009290 |
LS on intra-cell guard band configuration for NR-U |
RAN1 |
4.1 |
NE-DC, NGEN-DC, and NR-NR DC Maintenance [NR_newRAT-Core] |
|
R4-2006495 |
Introducing NE-DC combinations into specs |
Nokia |
R4-2006649 |
CR for 38.101-3: Corrections for Ppowerclass and referenced sections |
T-Mobile USA |
R4-2006650 |
Mirror CR for 38.101-3: Corrections for Ppowerclass and referenced sections |
T-Mobile USA |
R4-2006658 |
On introducing NE-DC combinations into specs |
ZTE Wistron Telecom AB |
R4-2007005 |
CR to TS 38.101-3: Clean up the MSD test point for ENDC(three band) |
ZTE Corporation |
R4-2007006 |
CR to TS 38.101-3: Clean up the MSD test point for ENDC(three band) |
ZTE Corporation |
R4-2008291 |
Email discussion summary for [95e][101] NR_NewRAT_SysParameters |
Moderator (ZTE) |
R4-2008382 |
CR for 38.101-3: Corrections for Ppowerclass and referenced sections |
T-Mobile USA |
R4-2008383 |
CR to TS 38.101-3: Clean up the MSD test point for ENDC(three band) |
ZTE Corporation |
R4-2008384 |
WF on supporting a new channel bandwidth added to an existing operating bands in a manner of release independence from Rel-15 |
ZTE |
R4-2008386 |
WF on support of 30k SCS for SSB of n38 and n39 |
Huawei |
R4-2008932 |
Email discussion summary for [95e][101] NR_NewRAT_SysParameters |
Moderator (ZTE) |
R4-2009155 |
WF on support of 30k SCS for SSB of n34, n38, n39 and n50 |
Huawei |
4.2 |
System Parameters Maintenance [NR_newRAT-Core] |
|
R4-2006584 |
On default SSB for band n34, n38, n39, n40, and n50 |
Nokia, Nokia Shanghai Bell |
R4-2006659 |
Support of release independence from Rel-15 |
ZTE Wistron Telecom AB |
R4-2006660 |
CR to TS 38.307 correction on support of release independence from Rel-15 |
ZTE Wistron Telecom AB |
R4-2006998 |
Discussion on CA nominal channel spacing without common u |
ZTE Corporation |
R4-2006999 |
CR to TS 38.101-1: Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2007000 |
CR to TS 38.101-1: Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2007001 |
CR to TS 38.104: Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2007002 |
CR to TS 38.104: Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2007007 |
Discussion on SSB pattern for NR bands supporting 30kHz SSB SCS |
ZTE Corporation |
R4-2007027 |
30k SSB SCS for Band n34, n39 and n50 |
Ericsson |
R4-2007028 |
30k SSB SCS for n50 |
Ericsson |
R4-2007029 |
30k SSB SCS for Band n34, n39 and n50 |
Ericsson |
R4-2007030 |
30k SSB SCS for n50 |
Ericsson |
R4-2007031 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2007032 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2007033 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2007034 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2007552 |
CR to TS37.104[R15]_Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2007553 |
CR to TS37.104[R16]_Correction on the CA nominal channel spacing catA |
ZTE Corporation |
R4-2007554 |
CR to TS37.141[R15]_Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2007555 |
CR to TS37.141[R16]_Correction on the CA nominal channel spacing catA |
ZTE Corporation |
R4-2008170 |
CR for 38.101-1 channel space for CA_Rel15 |
Huawei, HiSilicon |
R4-2008171 |
CR for 38.101-1 channel space for CA_Rel16 |
Huawei, HiSilicon |
R4-2008172 |
CR for 38.101-2 channel space for CA_Rel15 |
Huawei, HiSilicon |
R4-2008173 |
CR for 38.101-2 channel space for CA_Rel16 |
Huawei, HiSilicon |
R4-2008240 |
TS38.101-1 CR on 30KHz SSB SCS for n40 |
Huawei, HiSilicon, CMCC |
R4-2008241 |
TS38.101-1 CR on 30KHz SSB SCS for n40(Rel-16) |
Huawei, HiSilicon, CMCC |
R4-2008242 |
TS38.104 draft CR on 30KHz SSB SCS for n40 |
Huawei, HiSilicon, CMCC |
R4-2008243 |
TS38.104 draft CR on 30KHz SSB SCS for n40 (Rel-16) |
Huawei, HiSilicon, CMCC |
R4-2008244 |
Proposal on 30KHz SCS SSB for n50 and n38 |
Huawei, HiSilicon |
R4-2008385 |
CR to TS 38.307 correction on support of release independence from Rel-15 |
ZTE Wistron Telecom AB |
R4-2008387 |
30k SSB SCS for Band n34, n39 and n50 |
Ericsson |
R4-2008388 |
30k SSB SCS for Band n34, n39 and n50 |
Ericsson |
R4-2008389 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2008390 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2008391 |
CR to TS 38.101-1: Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2008392 |
CR to TS 38.104: Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2008393 |
CR to TS37.104[R15]_Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2008394 |
CR to TS37.141[R15]_Correction on the CA nominal channel spacing |
ZTE Corporation |
R4-2009157 |
30k SSB SCS for n50 |
Ericsson |
R4-2009158 |
30k SSB SCS for n50 |
Ericsson |
R4-2009159 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
R4-2009160 |
Addition of 30k SSB SCS for Band n38 |
Ericsson |
4.4.1 |
DC combination including NR carrier and/or NR CA combination maintenance [NR_newRAT-Core] |
|
R4-2008292 |
Email discussion summary for [95e][102] NR_NewRAT_UE_RF_Part_1 |
Moderator (Nokia) |
R4-2008933 |
Email discussion summary for [95e][102] NR_NewRAT_UE_RF_Part_1 |
Moderator (Nokia) |
4.4.1.1 |
Maintenance for bands and band combinations in 38.101-1 [NR_newRAT-Core] |
|
R4-2006135 |
Corrections of UE co-ex tables for Japan-related bands (R15) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2006136 |
Corrections of UE co-ex tables for Japan-related bands (R16) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2007025 |
CR for [agreed] asynchronous operation for NR CA n78-n79 |
NTT DOCOMO INC. |
R4-2007026 |
CR for [agreed] asynchronous operation for NR CA n78-n79 |
NTT DOCOMO INC. |
R4-2008395 |
CR for [agreed] asynchronous operation for NR CA n78-n79 |
NTT DOCOMO INC. |
R4-2008396 |
CR for [agreed] asynchronous operation for NR CA n78-n79 |
NTT DOCOMO INC. |
R4-2008970 |
Corrections of UE co-ex tables for Japan-related bands (R15) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2008971 |
Corrections of UE co-ex tables for Japan-related bands (R16) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2008972 |
Corrections of UE co-ex tables for Japan-related bands (R16) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
4.4.1.2 |
Maintenance for bands and band combinations in 38.101-2 [NR_newRAT-Core] |
|
R4-2006496 |
Proposed response to RAN2 LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
Nokia |
R4-2006577 |
Discussion on handling of fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
MediaTek inc. |
R4-2006578 |
Further reply LS on handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
MediaTek inc. |
R4-2006815 |
CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications |
MediaTek Inc. |
R4-2006816 |
CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications |
MediaTek Inc. |
R4-2006907 |
CR to TS 38.101-2 on corrections to intra-band CA band for FR2 (Rel-15) |
ZTE Corporation |
R4-2006908 |
CR to TS 38.101-2 on corrections to intra-band CA band for FR2 (Rel-16) |
ZTE Corporation |
R4-2008403 |
Further reply LS on handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
MediaTek inc. |
R4-2009156 |
Further reply LS on handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
MediaTek inc. |
4.4.1.3 |
Maintenance for combinations in 38.101-3 [NR_newRAT-Core] |
|
R4-2006137 |
Corrections of UE co-ex tables for Japan-related bands (R15) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2006138 |
Corrections of UE co-ex tables for Japan-related bands (R16) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2006342 |
CR Coexistence cleanup for 38101-3 Rel15 |
Apple Inc. |
R4-2006343 |
CR Coexistence cleanup for 38101-3 Rel16 |
Apple Inc. |
R4-2006452 |
CR for TS 38.101-3: Missing MSD due to cross band isolation |
MediaTek Inc. |
R4-2006453 |
CR for TS 38.101-3: Missing MSD due to cross band isolation |
MediaTek Inc. |
R4-2006454 |
CR for TS 38.101-3: MSD due to UL harmonic |
MediaTek Inc. |
R4-2006455 |
CR for TS 38.101-3: MSD due to UL harmonic |
MediaTek Inc. |
R4-2006457 |
CR for TR37.863-01-01: TP for missing MSD due to UL harmonic and cross band isolation for band combinations |
MediaTek Inc. |
R4-2006490 |
MOP for interband EN-DC including both FR1 and FR2 REL15 |
Nokia, Nokia Shanghai Bell |
R4-2006491 |
MOP for interband EN-DC including both FR1 and FR2 REL16 |
Nokia, Nokia Shanghai Bell |
R4-2008229 |
CR for 38.101-3 Correction on EN-DC synchronous carriers (R15) |
Huawei, HiSilicon |
R4-2008230 |
CR for 38.101-3 Correction on EN-DC synchronous carriers (R16) |
Huawei, HiSilicon |
R4-2008397 |
Corrections of UE co-ex tables for Japan-related bands (R15) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2008398 |
Corrections of UE co-ex tables for Japan-related bands (R16) |
SoftBank Corp., NTT docomo INC., KDDI Corporation |
R4-2008399 |
CR Coexistence cleanup for 38101-3 Rel15 |
Apple Inc. |
R4-2008400 |
CR for TS 38.101-3: Missing MSD due to cross band isolation |
MediaTek Inc. |
R4-2008401 |
CR for TS 38.101-3: Missing MSD due to cross band isolation |
MediaTek Inc. |
R4-2008402 |
CR for TR37.863-01-01: TP for missing MSD due to UL harmonic and cross band isolation for band combinations |
MediaTek Inc. |
4.4.2 |
[FR1] Maintenance for general requirements in 38.101-1 [NR_newRAT-Core] |
|
R4-2006143 |
Clarification on asymmetric channel bandwidth operation in FR1 |
Anritsu Corporation |
R4-2006144 |
CR to asymmetric CBW operation in FR1 |
Anritsu Corporation |
R4-2006145 |
CR to asymmetric CBW operation in FR1 |
Anritsu Corporation |
R4-2007003 |
CR to TS 38.101-1: Replace CBW with symbols defined in the specification. |
ZTE Corporation |
R4-2007004 |
CR to TS 38.101-1: Replace CBW with symbols defined in the specification. |
ZTE Corporation |
R4-2008224 |
CR for TS 38.101-1 UL configuration Correction for intra-band CA (R15) |
Huawei, HiSilicon |
R4-2008226 |
CR for 38.101-1 RFC corrections (R15) |
Huawei, HiSilicon |
R4-2008293 |
Email discussion summary for [95e][103] NR_NewRAT_UE_RF_Part_2 |
Moderator (MediaTek) |
R4-2008404 |
WF on EVM Requirement for UL MIMO Transmission |
Motorola Mobility |
R4-2008934 |
Email discussion summary for [95e][103] NR_NewRAT_UE_RF_Part_2 |
Moderator (MediaTek) |
4.4.2.1 |
Power class related to UL MIMO and other related req. (MPR, SEM, etc) [NR_newRAT-Core] |
|
R4-2006344 |
On transparent Tx_div |
Apple Inc. |
R4-2006366 |
Transparent Tx Diversity and Power Class 2 Ambiguity for Rel-15 NR |
Samsung |
R4-2006749 |
CR for UL MIMO requirements |
CMCC |
R4-2006817 |
NR UE power class for UL MIMO and 1-port transmission |
MediaTek Inc. |
R4-2006955 |
Correction to uplink antenna connectors |
Rohde & Schwarz |
R4-2006956 |
Correction to uplink antenna connectors |
Rohde & Schwarz |
R4-2007035 |
Correction of transmitter characteristics for UL-MIMO: powerclass 2 and fallback |
Ericsson |
R4-2007036 |
Correction of transmitter characteristics for UL-MIMO: powerclass 2 and fallback |
Ericsson |
R4-2007037 |
Remove power-class ambiguity for UL-MIMO PC2 capable UE configured for EN-DC |
Ericsson |
R4-2007071 |
Further on Rel-15 TxD requirements |
OPPO |
R4-2007072 |
Further on EN-DC and SA power class |
OPPO |
R4-2007073 |
Reply LS on Rel-15 TxD |
OPPO |
R4-2007074 |
Reply LS on Rel-15 UL MIMO power class |
OPPO |
R4-2007075 |
CR on transmit signal quality requirements for single antenna port |
OPPO |
R4-2008046 |
UL MIMO open items from WF and LS |
Qualcomm Incorporated |
R4-2008047 |
CR on UL MIMO changes MPR and emissions |
Qualcomm Incorporated |
R4-2008054 |
LS reply on requirement in Power Class 2 for UL MIMO Test cases. |
Qualcomm Incorporated |
R4-2008094 |
On the Need to Limit Delay for Transparent Transmit Diversity |
Motorola Mobility Germany GmbH |
R4-2008211 |
On Rel-15 PC2 power class |
Huawei, HiSilicon |
R4-2008212 |
On EN-DC power class |
Huawei, HiSilicon |
R4-2008213 |
On Rel-15 PC2 unwanted emissions and MPR requirement |
Huawei, HiSilicon |
R4-2008215 |
Draft CR on Rel-15 UL MIMO requirements |
Huawei, HiSilicon |
R4-2008256 |
Discussion on SA TxD Applicability |
vivo |
R4-2008257 |
Discussion on NSA Power Class 2 UE UL requirements for R15 |
vivo |
R4-2008258 |
Draft Reply LS on requirement in Power Class 2 for UL Test cases for GCF |
vivo |
R4-2008259 |
CR to 38.101-3: clarification of ENDC power class (Mirror for R16) |
vivo |
R4-2008260 |
CR to 38.101-1: UL MIMO MPR reference table (R15) |
vivo |
R4-2008261 |
CR to 38.101-1: UL MIMO MPR reference table (R16) |
vivo |
R4-2008276 |
Considerations on the EVM Definition for an Antenna Port or a Single MIMO Layer |
Motorola Mobility Germany GmbH |
R4-2008282 |
Remove power-class ambiguity for UL-MIMO PC2 capable UE configured for EN-DC |
Qualcomm Incorporated |
R4-2008294 |
Email discussion summary for [95e][104] NR_NewRAT_UE_RF_Part_3 |
Moderator (vivo) |
R4-2008408 |
WF on Power Class related UL MIMO and other requirements |
vivo |
R4-2008935 |
Email discussion summary for [95e][104] NR_NewRAT_UE_RF_Part_3 |
Moderator (vivo) |
4.4.2.2 |
Other Tx requirements [NR_newRAT-Core] |
|
R4-2006777 |
CR to 38.101-1: Revision to ULMIMO EVM spec |
Qualcomm Incorporated |
R4-2006778 |
CR to 38.101-1: Revision to ULMIMO EVM spec |
Qualcomm Incorporated |
R4-2006960 |
Correction to FR1 QPSK UL RMC |
Rohde & Schwarz |
R4-2006961 |
Correction to FR1 QPSK UL RMC |
Rohde & Schwarz |
R4-2007038 |
Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification |
Ericsson |
R4-2007039 |
Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification |
Ericsson |
R4-2007067 |
IBE measurements for half Pi BPSK with spectrum shaping |
Huawei, HiSilicon |
R4-2007068 |
IBE measurements for Pi/2 BPSK with spectrum shaping |
Huawei, HiSilicon |
R4-2008057 |
On the Transmit EVM Requirement for UL MIMO Transmission |
Motorola Mobility Germany GmbH |
R4-2008115 |
IBE requirement for almost contiguous allocations |
Qualcomm Incorporated |
R4-2008116 |
IBE requirement for almost contiguous allocations |
Qualcomm Incorporated |
R4-2008214 |
On UL MIMO Tx EVM requirement |
Huawei, HiSilicon |
R4-2008231 |
CR for 38.101-1 correction of delta SRS (R15) |
Huawei, HiSilicon |
R4-2008232 |
CR for 38.101-1 correction of delta SRS (R16) |
Huawei, HiSilicon |
R4-2008379 |
Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification |
Ericsson |
R4-2009177 |
Introduction of the Annex modifiedMPR-Behaviour into the NR SA specification |
Ericsson |
4.4.2.3 |
Maintenance for Receiver characteristics [NR_newRAT-Core] |
|
R4-2006383 |
CR to TS 38.101-1 R15: corrections on ACS for intra-band contiguous CA |
Xiaomi |
R4-2006384 |
CR to TS 38.101-1 R16: corrections on ACS for intra-band contiguous CA |
Xiaomi |
R4-2006385 |
CR to TS 38.101-3 R15: corrections on ACS for intra-band contiguous EN-DC |
Xiaomi |
R4-2006386 |
CR to TS 38.101-3 R16: corrections on ACS for intra-band contiguous EN-DC |
Xiaomi |
R4-2006953 |
Update of CSI-RS definition for FR1 DL RMCs |
Rohde & Schwarz |
R4-2006954 |
Update of CSI-RS definition for FR1 DL RMCs |
Rohde & Schwarz |
R4-2008073 |
CR for 38.101-1 to remove the NR CA configuration for REFSENS exception due to cross band isolation for CA |
Huawei, HiSilicon |
R4-2008074 |
CR for 38.101-1 to remove the NR CA configuration for REFSENS exception due to cross band isolation for CA (mirror CR) |
Huawei, HiSilicon |
R4-2008075 |
CR for 38.101-1 to add the REFSENS exception for inter band CA with SDL |
Huawei, HiSilicon |
R4-2008076 |
CR for 38.101-1 to add the REFSENS exception for inter band CA with SDL (mirror CR) |
Huawei, HiSilicon |
R4-2008077 |
CR for 38.101-1 to add requirements for inter-band CA with two UL bands |
Huawei, HiSilicon |
R4-2008078 |
CR for 38.101-1 to add requirements for inter-band CA with two UL bands (mirror CR) |
Huawei, HiSilicon |
R4-2008096 |
CR for 38.101-1 to remove the NR CA configuration for REFSENS exception due to cross band isolation for CA |
Huawei, HiSilicon |
R4-2008097 |
CR for 38.101-1 to add the REFSENS exception for inter band CA with SDL |
Huawei, HiSilicon |
R4-2008098 |
CR for 38.101-1 to add requirements for inter-band CA with two UL bands |
Huawei, HiSilicon |
R4-2008144 |
OOB blocking for n70 adjacent to n25 |
Qualcomm Incorporated |
R4-2008145 |
OOB blocking for n70 adjacent to n25 |
Qualcomm Incorporated |
R4-2008405 |
CR for 38.101-1 to add the REFSENS exception for inter band CA with SDL |
Huawei, HiSilicon |
R4-2008406 |
CR for 38.101-1 to add requirements for inter-band CA with two UL bands |
Huawei, HiSilicon |
R4-2008407 |
OOB blocking for n70 adjacent to n25 |
Qualcomm Incorporated |
R4-2008981 |
CR to TS 38.101-1 R15: corrections on ACS for intra-band contiguous CA |
Xiaomi |
R4-2008982 |
CR to TS 38.101-3 R15: corrections on ACS for intra-band contiguous EN-DC |
Xiaomi |
4.4.3 |
[FR2] Maintenance for general requirements in 38.101-2 [NR_newRAT-Core] |
|
R4-2006489 |
CR Correction for REL16 FR2 contiguous intraband CA configuration table |
Nokia, Qualcomm Inc, Ericsson |
R4-2007279 |
CR to K1 value in Annex A.3.3 of 38.101-2 |
Qualcomm Incorporated |
R4-2008295 |
Email discussion summary for [95e][105] NR_NewRAT_UE_RF_Part_4 |
Moderator (Apple) |
R4-2008409 |
WF on out-of-band blocking for DC in FR1 |
Antritsu |
R4-2008410 |
WF on WRC-19 outcome and impact on RAN4 specifications |
NTT DOCOMO |
R4-2008421 |
CR to K1 value in Annex A.3.3 of 38.101-2 |
Qualcomm Incorporated |
R4-2008936 |
Email discussion summary for [95e][105] NR_NewRAT_UE_RF_Part_4 |
Moderator (Apple) |
R4-2009141 |
WF on WRC-19 outcome and impact on RAN4 specifications |
NTT DOCOMO |
4.4.3.1 |
Regulatory Tx/Rx spurious emission limits handling [NR_newRAT-Core] |
|
R4-2006329 |
WRC-19 resolutions and impact to NR bands |
Apple Inc. |
R4-2006785 |
CR to 38.101-2: NS_202 update after changes to EU regulations |
Qualcomm Incorporated |
R4-2006786 |
CR to 38.101-2: NS_202 update after changes to EU regulations |
Qualcomm Incorporated |
R4-2006787 |
Incorporating WRC19 resolutions into FR2 specifications |
Qualcomm Incorporated |
R4-2006788 |
dCR to 38.101-2: Introduction of NS flags and A-MPR from WRC19 Resolutions |
Qualcomm Incorporated |
R4-2006789 |
CR to 38.101-2: Introduction of NS flags and A-MPR from WRC19 Resolutions |
Qualcomm Incorporated |
R4-2006790 |
On obsolescence of NS_201 |
Qualcomm Incorporated |
R4-2007077 |
Further on NS value report |
OPPO |
R4-2008277 |
CR for EESS protection for n257 |
NTT DOCOMO INC. |
R4-2008278 |
CR for EESS protection for n257 |
NTT DOCOMO INC. |
R4-2008279 |
[draft] LS for handling of WRC resolution |
NTT DOCOMO INC. |
R4-2008281 |
WRC-19 resolution for n257 and n259 |
NTT DOCOMO INC. |
4.4.3.2 |
Maintenance for Transmitter characteristics [NR_newRAT-Core] |
|
R4-2006150 |
CR on ACLR MBW definition in FR2 |
Anritsu Corporation, Skyworks Solutions Inc. |
R4-2006151 |
CR on ACLR MBW definition in FR2 |
Anritsu Corporation, Skyworks Solutions Inc. |
R4-2006330 |
Clarification for the definition of the UL duty cycle |
Apple Inc. |
R4-2006331 |
[draft] LS on clarification for the definition of the UL duty cycle |
Apple Inc. |
R4-2006355 |
CR to 38.101-2 on correction of reference point for beam correspondence side conditions |
Apple Inc. |
R4-2006356 |
CR to 38.101-2 on correction of reference point for beam correspondence side conditions R16 |
Apple Inc. |
R4-2006427 |
CR to TS38.101-2 on Rel-15 beam correspondence |
Samsung |
R4-2006823 |
CR for TS 38.101-2: Correction for configured transmitted power for CA |
MediaTek Inc. |
R4-2006824 |
CR for TS 38.101-2: Correction for configured transmitted power for CA |
MediaTek Inc. |
R4-2006962 |
Correction to FR2 QPSK UL RMC |
Rohde & Schwarz |
R4-2006963 |
Correction to FR2 QPSK UL RMC |
Rohde & Schwarz |
R4-2006964 |
Correction of Rel-16 UL RMCs |
Rohde & Schwarz |
R4-2007040 |
Correction of Pcmax for CA |
Ericsson |
R4-2007041 |
Correction of Pcmax for CA |
Ericsson |
R4-2007076 |
On max reference power in UL duty cycle capability |
OPPO |
R4-2008044 |
CR on Pcmax correction for CA |
Qualcomm Incorporated |
R4-2008045 |
Conflict between agreed WF and spec |
Qualcomm Incorporated |
R4-2008157 |
CR for for reference maximum transmission power for maxUplinkdutyCycle_Rel-15 |
Huawei, HiSilicon |
R4-2008158 |
CR for for reference maximum transmission power for maxUplinkdutyCycle_Rel-16 |
Huawei, HiSilicon |
R4-2008161 |
CR for intra-band CA DL Rx requirement-FR2_Rel-15 |
Huawei, HiSilicon |
R4-2008162 |
CR for intra-band CA DL Rx requirement-FR2_Rel-16 |
Huawei, HiSilicon |
R4-2008163 |
CR for modified MPR_Rel-15 |
Huawei, HiSilicon |
R4-2008164 |
CR for modified MPR_Rel-16 |
Huawei, HiSilicon |
R4-2008174 |
on reference power corresponding to maxUplinkdutyCycle |
Huawei, HiSilicon |
R4-2008252 |
On PTRS configuration for EVM requirement |
Huawei, HiSilicon |
R4-2008253 |
CR on PTRS configuration for UL RMC |
Huawei, HiSilicon |
R4-2008254 |
CR on PTRS configuration for UL RMC |
Huawei, HiSilicon |
R4-2008377 |
CR to TS38.101-2 on Rel-15 beam correspondence |
Samsung |
R4-2008416 |
CR for TS 38.101-2: Correction for configured transmitted power for CA |
MediaTek Inc. |
R4-2008417 |
CR on Pcmax correction for CA |
Qualcomm Incorporated |
R4-2008418 |
LS on clarification for the definition of the UL duty cycle |
RAN4 |
R4-2008419 |
CR for modified MPR_Rel-15 |
Huawei, HiSilicon |
R4-2008420 |
CR to 38.101-2 on correction of reference point for beam correspondence side conditions |
Apple Inc. |
R4-2008422 |
Correction to FR2 QPSK UL RMC |
Rohde & Schwarz |
R4-2008983 |
CR on Pcmax correction for CA |
Qualcomm Incorporated |
4.4.3.3 |
Maintenance for Receiver characteristics [NR_newRAT-Core] |
|
R4-2006825 |
CR for TS 38.101-2: Clarifications on transmitter power for receiver requirements |
MediaTek Inc. |
R4-2006826 |
CR for TS 38.101-2: Clarifications on transmitter power for receiver requirements |
MediaTek Inc. |
R4-2006957 |
Update of CSI-RS definition for FR2 DL RMCs |
Rohde & Schwarz |
R4-2006958 |
Update of CSI-RS definition for FR2 DL RMCs |
Rohde & Schwarz |
R4-2008009 |
ACS requirement correction |
Nokia, Nokia Shanghai Bell |
4.4.4 |
Maintenance for general requirements in 38.101-3 [NR_newRAT-Core] |
|
R4-2006487 |
FR1+FR2 CA interband CA BCS support REL15 |
Nokia, Nokia Shanghai Bell |
R4-2006488 |
FR1+FR2 CA interband CA BCS support REL16 |
Nokia, Nokia Shanghai Bell |
R4-2006635 |
CR to 38.101-3 MSD due to UL harmonics and intermodulation interference |
Apple Inc. |
R4-2006636 |
CR to 38.101-3 MSD due to UL harmonics and intermodulation interference R16 |
Apple Inc. |
R4-2008093 |
CR to 38.101-3 MSD due to UL harmonics and intermodulation interference R16 |
Apple Inc. |
R4-2008411 |
FR1+FR2 CA interband CA BCS support REL15 |
Nokia, Nokia Shanghai Bell |
R4-2008412 |
FR1+FR2 CA interband CA BCS support REL16 |
Nokia, Nokia Shanghai Bell |
R4-2008413 |
CR to 38.101-3 MSD due to UL harmonics and intermodulation interference |
Apple Inc. |
R4-2008414 |
CR to 38.101-3 MSD due to UL harmonics and intermodulation interference R16 |
Apple Inc. |
R4-2009152 |
CR to 38.101-3 MSD due to UL harmonics and intermodulation interference R16 |
Apple Inc. |
4.4.4.1 |
[FR1] Maintenance for Transmitter characteristics within FR1 [NR_newRAT-Core] |
|
R4-2006909 |
CR to TS 38.101-3 on configured output power relaxation due to EN-DC (Rel-15) |
ZTE Corporation |
R4-2006910 |
CR to TS 38.101-3 on configured output power relaxation due to EN-DC (Rel-16) |
ZTE Corporation |
R4-2007042 |
Removal of the Annex modifiedMPR-Behaviour from the NSA specification |
Ericsson |
R4-2007043 |
Removal of the Annex modifiedMPR-Behaviour from the NSA specification |
Ericsson |
R4-2008136 |
DC_2_n78 and DC_5_n78 with n48 coexistence |
Qualcomm Incorporated |
R4-2008141 |
DC_2_n78 and DC_5_n78 with n48 coexistence |
Qualcomm Incorporated |
R4-2008159 |
CR for 38.101-3 UE coexistence for Rel-15 |
Huawei, HiSilicon |
R4-2008160 |
CR for 38.101-3 UE coexistence for Rel-16 |
Huawei, HiSilicon |
R4-2008179 |
on serving cell number for ENDC power class |
Huawei, HiSilicon |
R4-2008180 |
LS on serving cell number for ENDC power class |
Huawei, HiSilicon |
R4-2008283 |
Coexistence DC_2_n78 and DC_5_n78 with band 48 |
Qualcomm Incorporated |
R4-2008380 |
Removal of the Annex modifiedMPR-Behaviour from the NSA specification |
Ericsson |
R4-2008415 |
LS on serving cell number for ENDC power class |
RAN4 |
R4-2008987 |
CR to remove TBD in 38.101-3 |
Qualcomm |
R4-2008988 |
CR to remove TBD in 38.101-3 |
Qualcomm |
R4-2009292 |
Removal of the Annex modifiedMPR-Behaviour from the NSA specification |
L.M. Ericsson Limited |
R4-2009293 |
Removal of the Annex modifiedMPR-Behaviour from the NSA specification |
L.M. Ericsson Limited |
4.4.4.3 |
[FR1] Maintenance for Receiver characteristics within FR1 [NR_newRAT-Core] |
|
R4-2006146 |
CR to out-of-band blocking for DC in FR1 |
Anritsu Corporation, Rohde&Schwarz, Keysight Technologies |
R4-2006147 |
CR to out-of-band blocking for DC in FR1 |
Anritsu Corporation, Rohde&Schwarz, Keysight Technologies |
R4-2006911 |
CR to TS 38.101-3 on REFSENS relaxation due to EN-DC (Rel-15) |
ZTE Corporation |
R4-2006912 |
CR to TS 38.101-3 on REFSENS relaxation due to EN-DC (Rel-16) |
ZTE Corporation |
R4-2008129 |
OOB blocking for n70 adjacent to n25 |
Qualcomm Incorporated |
R4-2008130 |
OOB blocking for n70 adjacent to n25 |
Qualcomm Incorporated |
4.4.5 |
Editorial CRs [NR_newRAT-Core] |
|
R4-2006148 |
CR on ACLR MBW definition in FR1 |
Anritsu Corporation, Skyworks Solutions Inc. |
R4-2006149 |
CR on ACLR MBW definition in FR1 |
Anritsu Corporation, Skyworks Solutions Inc. |
R4-2006390 |
CR to TS 38.101-3: editorial corrections on wide band Intermodulation for intra-band contiguous EN-DC in FR1 |
Xiaomi |
R4-2006392 |
CR to TS 38.101-3: editorial corrections on wide band Intermodulation for intra-band contiguous EN-DC in FR1 |
Xiaomi |
R4-2006846 |
CR on minor corrections to TS 38.101-1 (Rel-15) |
ZTE Corporation |
R4-2006870 |
CR on minor corrections to TS 38.101-1 (Rel-16) |
ZTE Corporation |
R4-2006903 |
CR on minor corrections to TS 38.101-2 (Rel-15) |
ZTE Corporation |
R4-2006904 |
CR on minor corrections to TS 38.101-2 (Rel-16) |
ZTE Corporation |
R4-2006905 |
CR on minor corrections to TS 38.101-3 (Rel-15) |
ZTE Corporation |
R4-2006906 |
CR on minor corrections to TS 38.101-3 (Rel-16) |
ZTE Corporation |
R4-2006939 |
Maintenance CR to 38101-1 on relative power tolerance R15 |
Huawei, HiSilicon |
R4-2006940 |
Maintenance CR to 38101-1 on relative power tolerance R16 |
Huawei, HiSilicon |
R4-2006941 |
Maintenance CR to 38307 on a reference spec number R15 |
Huawei, HiSilicon |
R4-2006942 |
Maintenance CR to 38307 on a reference spec number R16 |
Huawei, HiSilicon |
R4-2008984 |
CR to TS 38.101-3: editorial corrections on wide band Intermodulation for intra-band contiguous EN-DC in FR1 |
Xiaomi |
R4-2008985 |
CR to TS 38.101-3: editorial corrections on wide band Intermodulation for intra-band contiguous EN-DC in FR1 |
Xiaomi |
R4-2008986 |
CR on ACLR MBW definition in FR1 |
Anritsu Corporation, Skyworks Solutions Inc. |
4.5 |
UE EMC [NR_newRAT-Core] |
|
R4-2007060 |
CR to 38.124 on Exclusion Bands |
Ericsson |
R4-2007061 |
CR to 38.124 on Emissions and Immunity Applicability and ranges |
Ericsson |
R4-2007062 |
CR to TS 38.124 adding Methods of measurement and limits for EMC emissions |
Ericsson |
R4-2007063 |
CR to TS 38.124 on Definitions of Wired Network Port and UE |
Ericsson |
R4-2007064 |
CR to TS 38.124 adding Methods of measurement and limits for EMC immunity |
Ericsson |
R4-2007065 |
CR to 38.124 References for Arrangements for establishing a communication link |
Ericsson |
R4-2007066 |
CR to 38.124 on Emission Requirements |
Ericsson |
R4-2007444 |
CR to TS 38.124: specification corrections and removal of [], Rel-15 |
Huawei |
R4-2007445 |
CR to TS 38.124: correction of UE radiated spurious emissons requirement, Rel-15 |
Huawei |
R4-2007446 |
CR to TS 38.124: correction of the Rx exclusion band, Rel-15 |
Huawei |
R4-2007447 |
CR to TS 38.124: Performance assessment, Rel-15 |
Huawei |
R4-2007448 |
CR to TS 38.124: Performance criteria, Rel-15 |
Huawei |
R4-2007527 |
[EMC] CR TS38.124 conducted emissions |
ZTE Corporation |
R4-2007528 |
[EMC] CR TS38.124 CS |
ZTE Corporation |
R4-2007529 |
[EMC] CR TS38.124 dips |
ZTE Corporation |
R4-2007530 |
[EMC] CR TS38.124 EFT |
ZTE Corporation |
R4-2007531 |
[EMC] CR TS38.124 ESD |
ZTE Corporation |
R4-2007532 |
[EMC] CR TS38.124 references |
ZTE Corporation |
R4-2007533 |
[EMC] CR TS38.124 Rx exclusion band |
ZTE Corporation |
R4-2007534 |
[EMC] CR TS38.124 spurious radiated |
ZTE Corporation |
R4-2007535 |
[EMC] CR TS38.124 surge |
ZTE Corporation |
R4-2007536 |
[EMC] CR TS38.124 vehicular environment |
ZTE Corporation |
R4-2007537 |
[EMC] Discussion on Transients and surges in vehicular environment for NR UE_RZ |
ZTE Corporation |
R4-2008693 |
Email discussion summary for [95e][304] NR_EMC |
Moderator (ZTE) |
R4-2008716 |
CR to TS 38.124 adding Methods of measurement and limits for EMC emissions |
Ericsson |
R4-2008717 |
CR to TS 38.124: correction of UE radiated spurious emissons requirement, Rel-15 |
Huawei |
R4-2008718 |
CR to TS 38.124: correction of the Rx exclusion band, Rel-15 |
Huawei |
R4-2008719 |
[EMC] CR TS38.124 CS |
ZTE Corporation |
R4-2008720 |
[EMC] CR TS38.124 dips |
ZTE Corporation |
R4-2008721 |
[EMC] CR TS38.124 EFT |
ZTE Corporation |
R4-2008722 |
[EMC] CR TS38.124 ESD |
ZTE Corporation |
R4-2008723 |
[EMC] CR TS38.124 references |
ZTE Corporation |
R4-2008724 |
[EMC] CR TS38.124 surge |
ZTE Corporation |
R4-2008725 |
[EMC] CR TS38.124 vehicular environment |
ZTE Corporation |
R4-2008873 |
Email discussion summary for [95e][304] NR_EMC |
Moderator (ZTE) |
4.6 |
BS RF [NR_newRAT-Core] |
|
R4-2008691 |
Email discussion summary for [95e][302] NR_maintenance_RF_BS |
Moderator (Ericsson) |
R4-2008874 |
Email discussion summary for [95e][302] NR_maintenance_RF_BS |
Moderator (Ericsson) |
4.6.1 |
General [NR_newRAT-Core] |
|
R4-2006092 |
CR to TR 38.817-02: Corrections of CR implementation errors |
Nokia, Nokia Shanghai Bell |
R4-2006889 |
Views on frequency band support for HAPS-based deployment |
Google Inc., Loon Inc. |
R4-2006893 |
CR to TS 38.104 on frequency band support for HAPS-based deployment |
Google Inc., Loon Inc. |
R4-2006896 |
CR to TS 38.104 on frequency band support for HAPS-based deployment |
Google Inc., Loon Inc. |
R4-2006902 |
CR to TS 36.104 on frequency band support for HAPS-based deployment |
Google Inc., Loon Inc. |
R4-2006914 |
CR to TS 36.104 on frequency band support for HAPS-based deployment |
Google Inc., Loon Inc. |
R4-2007546 |
[R15]CR to TS 37.104 on channel spacing correction |
ZTE Corporation |
R4-2007548 |
[R15]CR to TS 37.141 on channel spacing correction |
ZTE Corporation |
R4-2007550 |
[R16]CR to TS 37.104 on channel spacing correction |
ZTE Corporation |
R4-2007551 |
[R16]CR to TS 37.141 on channel spacing correction |
ZTE Corporation |
R4-2008099 |
CR to 38.104 on Removal of brackets and TBD (Rel-15) |
Ericsson |
R4-2008100 |
CR to 38.104 on Removal of brackets and TBD (Rel-16) |
Ericsson |
R4-2008737 |
CR to 38.104 on Removal of brackets and TBD (Rel-16) |
Ericsson |
R4-2009055 |
CR to 38.104 on Removal of brackets and TBD (Rel-15) |
Ericsson |
4.6.3 |
Transmitter characteristics maintenance [NR_newRAT-Core] |
|
R4-2006293 |
WRC-19 protection requirements for EESS operation in 36-37GHz |
CATT |
R4-2006294 |
EESS protection requirements |
CATT |
R4-2006295 |
EESS protection requirements |
CATT |
R4-2006296 |
EESS protection requirements |
CATT |
R4-2006297 |
EESS protection requirements |
CATT |
R4-2007123 |
CR to TS 38.104: Additional OTA unwanted emissions requirements for EESS protection |
Nokia, Nokia Shanghai Bell |
R4-2007124 |
CR to TS 38.104: Additional OTA unwanted emissions requirements for EESS protection |
Nokia, Nokia Shanghai Bell |
R4-2007125 |
CR to TS 38.141-2: Additional OTA unwanted emissions requirements for EESS protection |
Nokia, Nokia Shanghai Bell |
R4-2007126 |
CR to TS 38.141-2: Additional OTA unwanted emissions requirements for EESS protection |
Nokia, Nokia Shanghai Bell |
R4-2007177 |
Unwanted emission requirements for EESS (36-37GHz) protection |
NTT DOCOMO, INC. |
R4-2007300 |
CR to 38.104: Additional requirements for EESS protection |
NEC |
R4-2007301 |
CR to 38.104: Additional requirements for EESS protection |
NEC |
R4-2007302 |
CR to 38.141-2: Additional requirements for EESS protection |
NEC |
R4-2007303 |
CR to 38.141-2: Additional requirements for EESS protection |
NEC |
R4-2007518 |
[BS RF][R15]CR to TS 38.104 on EESS protection 36--37GHz catF |
ZTE Corporation |
R4-2007519 |
[BS RF][R15]CR to TS 38.104 on EESS protection catF |
ZTE Corporation |
R4-2007520 |
[BS RF][R15]CR to TS 38.141-2 on EESS protection 36--37GHz catF |
ZTE Corporation |
R4-2007521 |
[BS RF][R15]CR to TS 38.141-2 on EESS protection catF |
ZTE Corporation |
R4-2007522 |
[BS RF][R16]CR to TS 38.104 on EESS protection 36--37GHz catA |
ZTE Corporation |
R4-2007523 |
[BS RF][R16]CR to TS 38.104 on EESS protection catA |
ZTE Corporation |
R4-2007524 |
[BS RF][R16]CR to TS 38.141-2 on EESS protection 36--37GHz catA |
ZTE Corporation |
R4-2007525 |
[BS RF][R16]CR to TS 38.141-2 on EESS protection catA |
ZTE Corporation |
R4-2007526 |
[BS RF]further discussion on the EESS protection for 36--37GHz outcome of WRC-19 |
ZTE Corporation |
R4-2008107 |
CR to 38.104 on EESS protection for bands n257 and n258 (Rel-15 |
Ericsson |
R4-2008108 |
CR to 38.104 on EESS protection for bands n257 and n258 (Rel-16) |
Ericsson |
R4-2008109 |
CR to 38.141-2 on EESS protection for bands n257 and n258 (Rel-15) |
Ericsson |
R4-2008110 |
CR to 38.141-2 on EESS protection for bands n257 and n258 (Rel-16) |
Ericsson |
R4-2008733 |
CR to 38.104 on EESS protection for bands n257 and n258 (Rel-15 |
Ericsson |
R4-2008734 |
CR to 38.141-2 on EESS protection for bands n257 and n258 (Rel-15) |
Ericsson |
R4-2008735 |
EESS protection requirements |
CATT |
R4-2008736 |
EESS protection requirements |
CATT |
R4-2009056 |
CR to 38.104 on EESS protection for bands n257 and n258 (Rel-15 |
Ericsson |
R4-2009057 |
CR to 38.141-2 on EESS protection for bands n257 and n258 (Rel-15) |
Ericsson |
4.6.4 |
Receiver characteristics maintenance [NR_newRAT-Core] |
|
R4-2006917 |
CR to TS 38.104: Correction to out-of-band blocking requirements in subclause 7.5 and subclause 10.6 |
Ericsson |
R4-2006918 |
CR to TS 38.104: Correction to out-of-band blocking requirements in subclause 7.5 and subclause 10.6 |
Ericsson |
R4-2008103 |
CR to 38.104 on Receiver spurious emissions exclusion band (Rel-15) |
Ericsson |
R4-2008104 |
CR to 38.104 on Receiver spurious emissions exclusion band (Rel-16) |
Ericsson |
R4-2008105 |
CR to 38.141-2 on Receiver spurious emissions exclusion band (Rel-15) |
Ericsson |
R4-2008106 |
CR to 38.141-2 on Receiver spurious emissions exclusion band (Rel-16) |
Ericsson |
R4-2008738 |
CR to 38.104 on Receiver spurious emissions exclusion band (Rel-15) |
Ericsson |
4.7 |
BS conformance testing [NR_newRAT-Perf] |
|
R4-2008692 |
Email discussion summary for [95e][303] NR_NewRAT_Conformance_BS |
Moderator (Futurewei) |
R4-2008739 |
WF on DM-RS windowing for TM2 |
Keysight, Rohde & Schwarz |
R4-2008740 |
WF on out of band CLTA maximum height |
Huawei |
R4-2008875 |
Email discussion summary for [95e][303] NR_NewRAT_Conformance_BS |
Moderator (Futurewei) |
4.7.1 |
General [NR_newRAT-Perf] |
|
R4-2007436 |
CR to 38.104: Annex B and C clarification on equlisation calculation (B.6, C.6) |
Keysight Technologies UK Ltd, Rohde & Schwarz |
R4-2007437 |
CR to 38.141-1: Annex H clarification on equlisation calculation (H.6) |
Keysight Technologies UK Ltd, Rohde & Schwarz |
R4-2007438 |
CR to 38.141-2: Annex L clarification on equlisation calculation (L.6) |
Keysight Technologies UK Ltd, Rohde & Schwarz |
R4-2007439 |
Detail information on Clarification on EVM equalizer calculation for NR BS conformance testing |
Keysight Technologies UK Ltd, Rohde & Schwarz |
R4-2007481 |
Discussion on EVM equalization for NR BS |
Nokia, Nokia Shanghai Bell |
4.7.3.1 |
eAAS specifications [NR_newRAT-Perf/Core] |
|
R4-2006093 |
CR to TS 37.145-2: Corrections on generation of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2006094 |
CR to TS 37.145-2: Corrections on generation of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2006459 |
TS 37.145-1: Corrections related to Foffset |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2006460 |
TS 37.145-2: Corrections related to Foffset |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2006462 |
TS 37.145-1: Corrections related to Foffset |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2006463 |
TS 37.145-2: Corrections related to Foffset |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2006915 |
CR to TS 37.145-2: Additional information about alignment needed for TRP measurements in Annex F.1 |
Ericsson |
R4-2006916 |
CR to TS 37.145-2: Additional information about alignment needed for TRP measurements in Annex F.1 |
Ericsson |
R4-2007418 |
CR to 37.145-1: Correction on interference level of receiver dynamic range requirement |
ZTE Corporation |
R4-2007419 |
CR to 37.145-1: Correction on interference level of receiver dynamic range requirement |
ZTE Corporation |
R4-2007420 |
CR to 37.145-2: Correction on interference level of receiver dynamic range requirement |
ZTE Corporation |
R4-2007421 |
CR to 37.145-2: Correction on interference level of receiver dynamic range requirement |
ZTE Corporation |
R4-2007459 |
CR to TS 37.105: removal of [], Rel-15 |
Huawei |
R4-2007460 |
CR to TS 37.105: removal of [], Rel-16 |
Huawei |
R4-2007470 |
CR to 37.145-2 Corrections to OTA modulation quality test Rel-15 |
Nokia, Nokia Shanghai Bell |
R4-2007471 |
CR to 37.145-2 Corrections to OTA modulation quality test Rel-16 |
Nokia, Nokia Shanghai Bell |
R4-2008013 |
CR to TS 37.145-2: Correcting the reference angular step equations (Annex F.2.2) |
Nokia, Nokia Shanghai Bell |
R4-2008015 |
CR to TS 37.145-2: Correcting the reference angular step equations (Annex F.2.2) |
Nokia, Nokia Shanghai Bell |
R4-2008741 |
CR to TS 37.105: removal of [], Rel-15 |
Huawei |
R4-2008742 |
CR to 37.145-2 Corrections to OTA modulation quality test Rel-15 |
Nokia, Nokia Shanghai Bell |
R4-2008745 |
CR to TS 37.145-2: Corrections on generation of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2008746 |
CR to TS 37.145-2: Additional information about alignment needed for TRP measurements in Annex F.1 |
Ericsson |
4.7.3.2 |
MSR specifications [NR_newRAT-Perf/Core] |
|
R4-2006458 |
TS 37.141: Corrections related to Foffset |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2006461 |
TS 37.141: Corrections related to Foffset |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007468 |
CR to 37.141 Rel-15 Corrections of references in Modulation quality test for NB-IoT |
Nokia, Nokia Shanghai Bell |
R4-2007469 |
CR to 37.141 Rel-16 Corrections of references in Modulation quality test for NB-IoT |
Nokia, Nokia Shanghai Bell |
R4-2007500 |
TS 37.141 - Issues with TC applicabilities for CS17 and CS18 |
Ericsson |
R4-2007501 |
CR to TS 37.141 Rel-15 - Issues with TC applicabilities CS17 |
Ericsson |
R4-2007502 |
CR to TS 37.141 Rel-16 - Issues with TC applicabilities CS17-CS18 |
Ericsson |
R4-2008062 |
CR to 37.141: Rel-15 corrections |
Nokia, Nokia Shanghai Bell |
R4-2008063 |
CR to 37.141: Rel |
Nokia, Nokia Shanghai Bell |
4.7.3.3 |
NR conformance testing specifications [NR_newRAT-Perf] |
|
R4-2006095 |
CR to TS 38.141-1: Corrections on generation of test configurations |
Nokia, Nokia Shanghai Bell, Ericsson |
R4-2006096 |
CR to TS 38.141-1: Corrections on generation of test configurations |
Nokia, Nokia Shanghai Bell, Ericsson |
R4-2006097 |
CR to TS 38.141-1: Clarifications and corrections on extreme test environment |
Nokia, Nokia Shanghai Bell, Ericsson |
R4-2006098 |
CR to TS 38.141-1: Clarifications and corrections on extreme test environment |
Nokia, Nokia Shanghai Bell, Ericsson |
R4-2006099 |
CR to TS 38.141-2: Correction on frequency offset symbols in test configurations |
Nokia, Nokia Shanghai Bell |
R4-2006100 |
CR to TS 38.141-2: Correction on frequency offset symbols in test configurations |
Nokia, Nokia Shanghai Bell |
R4-2006101 |
CR to TS 38.141-2: Correction on test procedure of OTA in-channel selectivity |
Nokia, Nokia Shanghai Bell |
R4-2006102 |
CR to TS 38.141-2: Correction on test procedure of OTA in-channel selectivity |
Nokia, Nokia Shanghai Bell |
R4-2006730 |
CR 38.141-1 Rel15 4.9.2.3 corrections for random data generation |
Futurewei |
R4-2006731 |
CR 38.141-1 Rel16 4.9.2.3 corrections for random data generation |
Futurewei |
R4-2006732 |
CR 38.141-2 Rel15 4.9.2.3 corrections for random data generation |
Futurewei |
R4-2006733 |
CR 38.141-2 Rel16 4.9.2.3 corrections for random data generation |
Futurewei |
R4-2007294 |
CR to TS 38.141-1: MU and TT value tables |
NEC |
R4-2007295 |
CR to TS 38.141-1: MU and TT value tables |
NEC |
R4-2007296 |
CR to TS 38.141-2: MU and TT value tables |
NEC |
R4-2007297 |
CR to TS 38.141-2: MU and TT value tables |
NEC |
R4-2007298 |
CR to TS 38.141-2: OTA receiver intermodulation interference signal type |
NEC |
R4-2007299 |
CR to TS 38.141-2: OTA receiver intermodulation interference signal type |
NEC |
R4-2007472 |
CR to 38.141-1 Rel-15 with correction to TPDR test procedure |
Nokia, Nokia Shanghai Bell |
R4-2007473 |
CR to 38.141-1 Rel-16 with correction to TPDR test procedure |
Nokia, Nokia Shanghai Bell |
R4-2007503 |
CR to TS 38.141-2 - Manufacturer declaration clarifications |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007504 |
CR to TS 38.141-2 - Manufacturer declaration clarifications |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007916 |
Discussion on out of band CLTA maximum height |
Huawei |
R4-2008041 |
CR to TS 38.141-2: Adding spherical angle definitions to 3.2 |
Nokia, Nokia Shanghai Bell |
R4-2008042 |
CR to TS 38.141-2: Adding spherical angle definitions to 3.2 |
Nokia, Nokia Shanghai Bell |
R4-2008043 |
CR to TS 38.141-2: Correcting the reference angular step equations (Annex I.2.2) |
Nokia, Nokia Shanghai Bell |
R4-2008055 |
CR to TS 38.141-2: Correcting the reference angular step equations (Annex I.2.2) |
Nokia, Nokia Shanghai Bell |
R4-2008743 |
CR to 38.141-1 Rel-15 with correction to TPDR test procedure |
Nokia, Nokia Shanghai Bell |
R4-2008747 |
CR to TS 38.141-2: Correction on frequency offset symbols in test configurations |
Nokia, Nokia Shanghai Bell |
R4-2008748 |
CR to TS 38.141-2: Correction on test procedure of OTA in-channel selectivity |
Nokia, Nokia Shanghai Bell |
R4-2009050 |
CR to TS 38.141-1: MU and TT value tables |
NEC |
4.7.4 |
Conducted conformance testing (38.141-1) [NR_newRAT-Perf] |
|
R4-2006919 |
CR to TS 38.141-1: Correction to out-of-band blocking requirement is subclause 7.5 |
Ericsson |
R4-2006920 |
CR to TS 38.141-1: Correction to out-of-band blocking requirement is subclause 7.5 |
Ericsson |
R4-2006922 |
CR to TS 38.141-2: Correction to out-of-band blocking requirement in subclause 7.6 |
Ericsson |
4.7.5 |
Radiated conformance testing (38.141-2) [NR_newRAT-Perf] |
|
R4-2006921 |
CR to TS 38.141-2: Correction to out-of-band blocking requirement in subclause 7.6 |
Ericsson |
R4-2007313 |
NR FR2 test models for 16QAM |
Huawei, HiSilicon |
R4-2007314 |
NR FR2 test models for 16QAM |
Huawei, HiSilicon |
R4-2007315 |
CR for TS 38.141-2: Total power dynamic range |
Huawei, HiSilicon |
R4-2007316 |
CR for TS 38.141-2: Total power dynamic range |
Huawei, HiSilicon |
R4-2007442 |
CR to TS 38.141-2: Corrections for the extreme environment testing, Rel-15 |
Huawei |
R4-2007443 |
CR to TS 38.141-2: Corrections for the extreme environment testing, Rel-16 |
Huawei |
R4-2008744 |
CR for TS 38.141-2: Total power dynamic range |
Huawei, HiSilicon |
4.8.2.1 |
Emission requirements [NR_newRAT-Core] |
|
R4-2007449 |
Further clarifications to the direct field strength measurement of unwanted radiated emissions from the BS enclosure port |
Huawei |
R4-2007450 |
CR to TS 38.113: direct field strength measurements for the EMC RE, Rel-15 |
Huawei |
R4-2008727 |
CR to TS 38.113: direct field strength measurements for the EMC RE, Rel-15 |
Huawei |
R4-2009061 |
WF on MSR base station TC reduction. |
Ericsson |
4.8.3 |
Performance requirements [NR_newRAT-Perf] |
|
R4-2007058 |
Proposal for EMC reduction of test configurations |
Ericsson |
R4-2007059 |
Draft CR to 37.113 Introducing Reverberation Chamber |
Ericsson, ZTE |
R4-2007547 |
[R15]CR to TS 37.114 Add the reverberation chamber for radiated immunity testing (clause 2 |
ZTE Corporation |
R4-2007549 |
[R15]CR to TS 38.113 Add the reverberation chamber for radiated immunity testing (clause 2 |
ZTE Corporation |
R4-2008726 |
Draft CR to 37.113 Introducing Reverberation Chamber |
Ericsson, ZTE |
R4-2008728 |
[R15]CR to TS 37.114 Add the reverberation chamber for radiated immunity testing (clause 2 |
ZTE Corporation |
R4-2008729 |
[R15]CR to TS 38.113 Add the reverberation chamber for radiated immunity testing (clause 2 |
ZTE Corporation |
4.9 |
RRM core maintenance (38.133/36.133) [NR_newRAT-Core] |
|
R4-2006602 |
Correction of CFRA RSRP threshold |
Nokia, Nokia Shanghai Bell |
R4-2006603 |
Correction of CFRA RSRP threshold |
Nokia, Nokia Shanghai Bell |
R4-2008490 |
Email discussion summary for [95e][201] NR_NewRAT_RRM_Core |
Moderator (Huawei, HiSilicon) |
R4-2008522 |
Email discussion summary for [95e][233] NR_RRM_maintenance |
Moderator (Apple) |
R4-2008527 |
WF on maintenance topics for NR RRM signalling characteristics |
Apple |
R4-2009013 |
Email discussion summary for [95e][201] NR_NewRAT_RRM_Core |
Moderator (Huawei, HiSilicon) |
R4-2009095 |
Email discussion summary for [95e][233] NR_RRM_maintenance |
Moderator (Apple) |
R4-2009258 |
Email discussion summary for [95e][233] NR_RRM_maintenance |
Moderator (Apple) |
4.9.2 |
Editorial CRs [NR_newRAT-Core] |
|
R4-2006027 |
[CR] Editorial corrections for 38.133 R15 Core Part |
ZTE Corporation |
R4-2006028 |
[CR] Editorial corrections for 38.133 R16 Core Part - Cat A |
ZTE Corporation |
R4-2006029 |
[CR] Editorial corrections for 38.133 R16 Core Part - Cat F |
ZTE Corporation |
R4-2006218 |
Rapportuer CR for TS38.133 |
Apple |
R4-2006880 |
CR on TS38.133 for modification on number of cells and number of SSB to be measured for FR2 intra-frequency measurement |
Mediatek Inc., Huawei, Hisilicon, Apple, Intel |
R4-2006881 |
CR on TS38.133 for modification on number of cells and number of SSB to be measured for FR2 intra-frequency measurement |
Mediatek Inc., Huawei, Hisilicon, Apple, Intel |
R4-2007714 |
Editoral CR on TS 38.133 Rel-16 (Cat A) |
Huawei, Hisilicon |
R4-2007715 |
Editoral CR on TS 38.133 Rel-15 |
Huawei, Hisilicon |
R4-2008660 |
[CR] Editorial corrections for 38.133 R15 Core Part |
ZTE Corporation |
R4-2008661 |
Rapportuer CR for TS38.133 |
Apple |
R4-2009106 |
Rapportuer CR for TS38.133 |
Apple |
R4-2009271 |
Rapportuer CR for TS38.133 |
Apple |
R4-2009272 |
Rapportuer CR for TS38.133 |
Apple |
4.9.3 |
UE measurement capability (38.133/36.133) [NR_newRAT-Core] |
|
R4-2006878 |
CR on TS38.133 for modification of the layer 3 and layer 1 measurement sharing factor when both SSB and RSSI symbol to be measured are considered |
Mediatek Inc., Huawei, Hisilicon, Apple |
R4-2006879 |
CR on TS38.133 for modification of the layer 3 and layer 1 measurement sharing factor when both SSB and RSSI symbol to be measured are considered |
Mediatek Inc., Huawei, Hisilicon, Apple |
R4-2007638 |
CR to 36.133 on NR reporting criteria |
ZTE |
R4-2007639 |
CR to 36.133 on NR reporting criteria |
ZTE |
R4-2007709 |
CR on NR reporting criteria for EN-DC (Cat A) |
Huawei, Hisilicon |
R4-2007710 |
CR on NR reporting criteria for EN-DC |
Huawei, Hisilicon |
R4-2007713 |
Discussion on reporting criteria for EN-DC |
Huawei, Hisilicon |
R4-2007805 |
CR on FR2 measurement requirements outside gaps R15 |
Huawei, HiSilicon, MediaTek, Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007806 |
CR on FR2 measurement requirements outside gaps R16 |
Huawei, HiSilicon, MediaTek, Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007807 |
CR to remove RSTD requirements for NE-DC in 36.133 R15 |
Huawei, HiSilicon |
R4-2007808 |
CR to remove RSTD requirements for NE-DC in 36.133 R16 |
Huawei, HiSilicon |
R4-2007809 |
CR on inter-RAT RSTD requirements for NE-DC in 38.133 R15 |
Huawei, HiSilicon |
R4-2007810 |
CR on inter-RAT RSTD requirements for NE-DC in 38.133 R16 |
Huawei, HiSilicon |
R4-2007961 |
NR reporting criteria |
Ericsson |
R4-2007962 |
NR reporting criteria |
Ericsson |
R4-2008525 |
CR on NR reporting criteria for EN-DC |
Huawei, Hisilicon |
R4-2009122 |
CR to 36.133 on NR reporting criteria |
ZTE |
4.9.4 |
RRM measurement and measurement gap (38.133/36.133) [NR_newRAT-Core] |
|
R4-2006185 |
CR on CSSF correction for R15 TS38.133 |
Apple |
R4-2006186 |
CR on CSSF correction for R16 TS38.133 |
Apple |
R4-2007757 |
Correction on gap pattern applicability in TS 36.133 R15 |
Huawei, Hisilicon |
R4-2007758 |
Correction on gap pattern applicability in TS 36.133 R16 |
Huawei, Hisilicon |
R4-2008526 |
CR on CSSF correction for R15 TS38.133 |
Apple |
4.9.5 |
Connected state mobility (38.133/36.133) [NR_newRAT-Core] |
|
R4-2006002 |
[CR] RRC release with redirection 38.133 R16 |
ZTE Corporation |
R4-2006003 |
[CR] RRC release with redirection 36.133 R15 |
ZTE Corporation |
R4-2006004 |
[CR] RRC release with redirection 36.133 R16 Cat A |
ZTE Corporation |
R4-2006005 |
Discussion on RRC procedure delay in RRC release with redirection |
ZTE Corporation |
R4-2006006 |
Discussion on RRC re-establishment requirement |
ZTE Corporation |
R4-2006007 |
CR on RRC re-establishment requirements R15 |
ZTE Corporation |
R4-2006008 |
CR on RRC re-establishment requirements R16 (Cat A) |
ZTE Corporation |
R4-2007981 |
Correction to RRC release with redirection requirements in 36.133 Rel-15 |
Ericsson |
R4-2007982 |
Correction to RRC release with redirection requirements in 36.133 Rel-16 |
Ericsson |
4.9.6 |
Timing (38.133/36.133) [NR_newRAT-Core] |
|
R4-2007711 |
CR on UE transmit timing (Cat A) |
Huawei, Hisilicon |
R4-2007712 |
CR on UE transmit timing |
Huawei, Hisilicon |
4.9.7 |
Signaling characteristics (38.133/36.133) [NR_newRAT-Core] |
|
R4-2006174 |
Corrections to R15 MAC-CE based TCI state switching requirements |
Qualcomm Incorporated |
R4-2006177 |
CR for correction to MAC-CE based TCI State switch timeline (Clause 8.10.3) |
Qualcomm Incorporated, MediaTek |
R4-2006178 |
CR for correction to MAC-CE based TCI State switch timeline (Clause 8.10.3) |
Qualcomm Incorporated, MediaTek |
R4-2006189 |
On issues of R15 BWP switching delay requirement |
Apple |
R4-2006190 |
CR on BWP switching delay requirement for R15 |
Apple |
R4-2006191 |
CR on BWP switching delay requirement for R16 |
Apple |
R4-2006209 |
CR on Active TCI State Switching requirements - Rel15 |
Apple |
R4-2006210 |
CR on Active TCI State Switching requirements - Rel16 |
Apple, Qualcomm |
R4-2006465 |
CR on TCI state switch |
MediaTek inc. |
R4-2006466 |
CR on TCI state switch |
MediaTek inc. |
R4-2006847 |
CR for SCell activation delay in FR2 |
MediaTek inc. |
R4-2006848 |
CR for SCell activation delay in FR2 |
MediaTek inc. |
R4-2006891 |
[CR] TCI state switch delay 38.133 R15 |
ZTE Corporation |
R4-2006892 |
[CR] TCI state switch delay 38.133 R16 Cat A |
ZTE Corporation |
R4-2007280 |
CR to T parameters in 8.3.2 of 38.133 |
Qualcomm Incorporated |
R4-2007659 |
CR on LTE SCell activation and deactivation delay |
Huawei, Hisilicon |
R4-2007660 |
CR on LTE SCell activation and deactivation delay_r16 |
Huawei, Hisilicon |
R4-2007661 |
CR on SCell activation and deactivation delay |
Huawei, Hisilicon |
R4-2007662 |
CR on SCell activation and deactivation delay_r16 |
Huawei, Hisilicon |
R4-2007663 |
CR on Psharingfactor |
Huawei, Hisilicon |
R4-2007664 |
CR on Psharingfactor_r16 |
Huawei, Hisilicon |
R4-2007705 |
CR on CSI-RS based RLM requirement (Cat A) |
Huawei, Hisilicon |
R4-2007706 |
CR on CSI-RS based RLM requirement |
Huawei, Hisilicon |
R4-2007707 |
CR on interruption due to Acitve BWP switch (Cat A) |
Huawei, Hisilicon |
R4-2007708 |
CR on interruption due to Acitve BWP switch |
Huawei, Hisilicon |
R4-2007751 |
Correction onTCI state switching R15 |
Huawei, Hisilicon |
R4-2007752 |
Correction onTCI state switching R16 |
Huawei, Hisilicon |
R4-2007780 |
CR 38.133 (8.10.5) Corrections to RRC-based TCI state change |
Ericsson |
R4-2007781 |
CR 38.133 (8.10.5) Corrections to RRC-based TCI state change |
Ericsson |
R4-2007783 |
CR 38.133 (8.3.2) Corrections to SCell Activation delay requirements |
Ericsson |
R4-2007784 |
CR 38.133 (8.3.2) Corrections to SCell Activation delay requirements |
Ericsson, MediaTek |
R4-2007811 |
Discussion on SCell activation requirements |
Huawei, HiSilicon |
R4-2007812 |
CR on SCell activation requirements R15 |
Huawei, HiSilicon |
R4-2007813 |
CR on SCell activation requirements R16 |
Huawei, HiSilicon |
R4-2007963 |
Clarification on RLM |
Ericsson |
R4-2007964 |
Clarification on RLM |
Ericsson |
R4-2008528 |
CR on LTE SCell activation and deactivation delay |
Huawei, Hisilicon |
R4-2008529 |
CR 38.133 (8.3.2) Corrections to SCell Activation delay requirements |
Ericsson, MediaTek |
R4-2008530 |
CR for SCell activation delay in FR2 |
MediaTek inc. |
R4-2008531 |
CR on Active TCI State Switching requirements - Rel15 |
Apple, Qualcomm |
R4-2008532 |
[CR] TCI state switch delay 38.133 R15 |
ZTE Corporation |
R4-2008535 |
CR on TCI state switch |
MediaTek inc. |
R4-2008536 |
CR on TCI state switch |
MediaTek inc. |
R4-2008537 |
CR on BWP switching delay requirement for R15 |
Apple |
R4-2008541 |
CR on Psharingfactor |
Huawei, Hisilicon |
R4-2009125 |
CR on SCell activation requirements R15 |
Huawei, HiSilicon |
R4-2009273 |
CR 38.133 (8.3.2) Corrections to SCell Activation delay requirements |
Ericsson, MediaTek |
4.9.8 |
Beam management based on SSB and/or CSI-RS (38.133) [NR_newRAT-Core] |
|
R4-2006187 |
CR on SMTC2 configuration in SSB based CBD for R15 |
Apple |
R4-2006188 |
CR on SMTC2 configuration in SSB based CBD for R16 |
Apple |
R4-2006849 |
Semi-persistent or aperiodic SSB based L1-RSRP reporting on PUSCH in FR2 |
MediaTek inc. |
R4-2006850 |
CR for Semi-persistent or aperiodic SSB based L1-RSRP reporting on PUSCH in FR2 |
MediaTek inc. |
R4-2006851 |
CR for Semi-persistent or aperiodic SSB based L1-RSRP reporting on PUSCH in FR2 |
MediaTek inc. |
R4-2006852 |
CR on SMTC period for beam management requirements |
MediaTek inc., Huawei, HiSilicon |
R4-2006853 |
CR on SMTC period for beam management requirements |
MediaTek inc., Huawei, HiSilicon |
R4-2006854 |
CR for CSI-RS based L1-RSRP measurement period |
MediaTek inc. |
R4-2006855 |
CR for CSI-RS based L1-RSRP measurement period |
MediaTek inc. |
R4-2007492 |
Applicability of QCL |
Qualcomm |
R4-2007493 |
Applicability of QCL |
Qualcomm |
R4-2007814 |
Discussion on SSB based L1-RSRP measurement |
Huawei, HiSilicon |
R4-2007815 |
CR on SSB based L1-RSRP measurement R15 |
Huawei, HiSilicon |
R4-2007816 |
CR on SSB based L1-RSRP measurement R16 |
Huawei, HiSilicon |
R4-2008533 |
CR on SMTC period for beam management requirements |
MediaTek inc., Huawei, HiSilicon |
R4-2008534 |
Applicability of QCL |
Qualcomm |
R4-2009105 |
Applicability of QCL |
Qualcomm |
4.10 |
RRM perf maintenance (38.133/36.133) [NR_newRAT-Perf] |
|
R4-2008491 |
Email discussion summary for [95e][202] NR_NewRAT_RRM_Perf |
Moderator (Ericsson) |
R4-2008538 |
WF on rough/fine beam assumption |
Anritsu |
R4-2009014 |
Email discussion summary for [95e][202] NR_NewRAT_RRM_Perf |
Moderator (Ericsson) |
4.10.1 |
General [NR_newRAT-Perf] |
|
R4-2006467 |
CR on PDSCH RMC |
MediaTek inc. |
R4-2006468 |
CR on PDSCH RMC |
MediaTek inc. |
R4-2007665 |
CR on E-UTRAN Serving Cell Parameters |
Huawei, Hisilicon |
R4-2007666 |
CR on E-UTRAN Serving Cell Parameters_r16 |
Huawei, Hisilicon |
R4-2007667 |
CR on Modified parameters for BFD TCs with 4Rx antenna |
Huawei, Hisilicon |
R4-2007668 |
CR on Modified parameters for BFD TCs with 4Rx antenna_r16 |
Huawei, Hisilicon |
R4-2007753 |
Accuracy of carrier aggregation in NR R15 |
Huawei, Hisilicon |
R4-2007754 |
Accuracy of carrier aggregation in NR R16 |
Huawei, Hisilicon |
R4-2008542 |
CR on E-UTRAN Serving Cell Parameters |
Huawei, Hisilicon |
R4-2008543 |
CR on Modified parameters for BFD TCs with 4Rx antenna |
Huawei, Hisilicon |
4.10.2 |
Editorial CRs [NR_newRAT-Perf] |
|
R4-2006030 |
[CR] Editorial corrections for 38.133 R15 Perf Part |
ZTE Corporation |
R4-2006031 |
[CR] Editorial corrections for 38.133 R16 Perf Part - Cat A |
ZTE Corporation |
R4-2006064 |
[CR] Editorial corrections for 38.133 R16 Perf Part - Cat F |
ZTE Corporation |
R4-2008659 |
[CR] Editorial corrections for 38.133 R15 Perf Part |
ZTE Corporation |
4.10.3 |
RRM test cases [NR_newRAT-Perf] |
|
R4-2006071 |
CR to Intra-frequency handover from FR1 to FR1 |
ANRITSU LTD |
R4-2006072 |
CR to Intra-frequency handover from FR1 to FR1 |
ANRITSU LTD |
R4-2006073 |
CR to SA event triggered reporting tests with per-UE gaps |
ANRITSU LTD |
R4-2006074 |
CR to SA event triggered reporting tests with per-UE gaps |
ANRITSU LTD |
R4-2006075 |
CR to A.6.1.2.1 Cell reselection to higher priority E-UTRAN |
ANRITSU LTD |
R4-2006076 |
CR to A.6.1.2.1 Cell reselection to higher priority E-UTRAN |
ANRITSU LTD |
R4-2006077 |
Correction to General test parameters in A.6.6.1.2 |
ANRITSU LTD |
R4-2006078 |
Correction to General test parameters in A.6.6.1.2 |
ANRITSU LTD |
R4-2006079 |
CR to E-UTRAN |
ANRITSU LTD |
R4-2006080 |
CR to E-UTRAN |
ANRITSU LTD |
R4-2006081 |
CR to SA NR- E-UTRAN event-triggered reporting in FR1 |
ANRITSU LTD |
R4-2006179 |
Corrections to Inter-freq SMTC configurations in A.4.7.1.2 and A.4.7.2.2 |
Qualcomm Incorporated |
R4-2006180 |
Corrections to Inter-freq SMTC configurations in A.4.7.1.2 and A.4.7.2.2 |
Qualcomm Incorporated |
R4-2006387 |
Add UE Beam assumption for RRM Test cases in A.7.3, A.7.4, A.7.7 |
ANRITSU LTD |
R4-2006388 |
Add UE Beam assumption for RRM Test cases in A.7.3, A.7.4, A.7.7 |
ANRITSU LTD |
R4-2006389 |
Add UE Beam assumption for RRM Test cases in A.5.3, A.5.4, A.5.7 |
ANRITSU LTD |
R4-2006391 |
Add UE Beam assumption for RRM Test cases in A.5.3, A.5.4, A.5.7 |
ANRITSU LTD |
R4-2006436 |
Update of FR2 RLM Test cases with 2 Angles of Arrival |
ANRITSU LTD |
R4-2006437 |
Update of FR2 RLM Test cases with 2 Angles of Arrival |
ANRITSU LTD |
R4-2006438 |
Update of Tx Timing Test cases |
ANRITSU LTD |
R4-2006439 |
Update of Tx Timing Test cases |
ANRITSU LTD |
R4-2006441 |
Update of FR2 RLM and BFD-LR Test cases |
ANRITSU LTD |
R4-2006442 |
Update of FR2 RLM and BFD-LR Test cases |
ANRITSU LTD |
R4-2006443 |
Update of FR2 SS-RSRP Test cases |
ANRITSU LTD |
R4-2006444 |
Update of FR2 SS-RSRP Test cases |
ANRITSU LTD |
R4-2006856 |
CR on RACH test cases with CSI-RS resource R15 |
MediaTek inc. |
R4-2006857 |
CR on RACH test cases with CSI-RS resource R16 |
MediaTek inc. |
R4-2006988 |
Correction of NR SA FR2 inter-freq measurement reporting |
Ericsson |
R4-2006989 |
Correction of NR SA FR2 inter-freq measurement reporting |
Ericsson |
R4-2007176 |
UE Beam assumption for RRM Test cases in 38.133 Annex A |
ANRITSU LTD |
R4-2007391 |
CR: Correction of L1-RSRP measurement period |
Ericsson, Huawei, HiSilicon |
R4-2007392 |
CR: Correction of L1-RSRP measurement period |
Ericsson, Huawei, HiSilicon |
R4-2007428 |
CR to TS 38.133: Correction to CSI-RS configurations in A.3.14 (Rel-15) |
Rohde & Schwarz |
R4-2007429 |
CR to TS 38.133: Correction to CSI-RS configurations in A.3.14 (Rel-16) |
Rohde & Schwarz |
R4-2007430 |
CR to TS 38.133: Correction to SMTC configuration in measurement accuracy tests (Rel-15) |
Rohde & Schwarz |
R4-2007431 |
CR to TS 38.133: Correction to SMTC configuration in measurement accuracy tests (Rel-16) |
Rohde & Schwarz |
R4-2007432 |
CR to TS 38.133: Clarifications to AoA setup Annex A.5 (Rel-15) |
Rohde & Schwarz |
R4-2007433 |
CR to TS 38.133: Clarifications to AoA setup Annex A.5 (Rel-16) |
Rohde & Schwarz |
R4-2007434 |
CR to TS 38.133: Clarifications to AoA setup Annex A.7 (Rel-15) |
Rohde & Schwarz |
R4-2007435 |
CR to TS 38.133: Clarifications to AoA setup Annex A.7 (Rel-16) |
Rohde & Schwarz |
R4-2007669 |
CR on BFD TCs |
Huawei, Hisilicon |
R4-2007670 |
CR on BFD TCs_r16 |
Huawei, Hisilicon |
R4-2007671 |
CR on UL carrier RRC reconfiguration Delay TC |
Huawei, Hisilicon |
R4-2007672 |
CR on UL carrier RRC reconfiguration Delay TC_r16 |
Huawei, Hisilicon |
R4-2007673 |
CR to FR1 SCell activation delay test cases |
Huawei, Hisilicon |
R4-2007674 |
CR to FR1 SCell activation delay test cases_r16 |
Huawei, Hisilicon |
R4-2007675 |
CR to inter-frequency measurement TCs |
Huawei, Hisilicon |
R4-2007676 |
CR to inter-frequency measurement TCs_r16 |
Huawei, Hisilicon |
R4-2007677 |
CR to interruption TCs |
Huawei, Hisilicon |
R4-2007678 |
CR to interruption TCs_r16 |
Huawei, Hisilicon |
R4-2007679 |
CR to FR1 SA inter-RAT measurement TCs_r16 |
Huawei, Hisilicon |
R4-2007716 |
CR on RRC Connection Release with Redirection (Cat A) |
Huawei, Hisilicon |
R4-2007717 |
CR on RRC Connection Release with Redirection test cases |
Huawei, Hisilicon |
R4-2007718 |
CR on RRC Re-establishment test cases (Cat A) |
Huawei, Hisilicon |
R4-2007719 |
CR on RRC Re-establishment test cases |
Huawei, Hisilicon |
R4-2007720 |
CR on Timing advance test cases for EN-DC (Cat A) |
Huawei, Hisilicon |
R4-2007721 |
CR on Timing advance test cases for EN-DC |
Huawei, Hisilicon |
R4-2007722 |
CR on Timing test cases for NR SA (Cat A) |
Huawei, Hisilicon |
R4-2007723 |
CR on Timing test cases for NR SA |
Huawei, Hisilicon |
R4-2007817 |
CR on L1-RSRP delay tests for FR2 R15 |
Huawei, HiSilicon |
R4-2007818 |
CR on L1-RSRP delay tests for FR2 R16 |
Huawei, HiSilicon |
R4-2007819 |
CR to L1-RSRP accuracy TC for FR2 EN-DC R15 |
Huawei, HiSilicon |
R4-2007820 |
CR to L1-RSRP accuracy TC for FR2 EN-DC R16 |
Huawei, HiSilicon |
R4-2007821 |
CR to L1-RSRP accuracy TC for FR2 SA R15 |
Huawei, HiSilicon |
R4-2007822 |
CR to L1-RSRP accuracy TC for FR2 SA R16 |
Huawei, HiSilicon |
R4-2007823 |
CR to TCI state switch TC R15 |
Huawei, HiSilicon |
R4-2007824 |
CR to TCI state switch TC R16 |
Huawei, HiSilicon |
R4-2008539 |
CR to Intra-frequency handover from FR1 to FR1 |
ANRITSU LTD |
R4-2008544 |
CR on BFD TCs |
Huawei, Hisilicon |
R4-2008545 |
CR on UL carrier RRC reconfiguration Delay TC |
Huawei, Hisilicon |
R4-2008546 |
CR to FR1 SCell activation delay test cases |
Huawei, Hisilicon |
R4-2008547 |
CR to inter-frequency measurement TCs |
Huawei, Hisilicon |
R4-2008548 |
CR to interruption TCs |
Huawei, Hisilicon |
R4-2008549 |
CR to FR1 SA inter-RAT measurement TCs_r16 |
Huawei, Hisilicon |
R4-2008550 |
CR to interruption TCs_r16 |
Huawei, Hisilicon |
R4-2009115 |
CR to TS 38.133: Correction to CSI-RS configurations in A.3.14 (Rel-15) |
Rohde & Schwarz |
4.11 |
Demodulation and CSI maintenance [NR_newRAT-Perf] |
|
R4-2008701 |
Email discussion summary for [95e][312] Demod_Maintenance |
Moderator (Intel) |
R4-2008876 |
Email discussion summary for [95e][312] Demod_Maintenance |
Moderator (Intel) |
4.11.1 |
Editorial CRs [NR_newRAT-Perf] |
|
R4-2006688 |
CR for correction of Angle of Arrival for Radiated Requirements in section 4 |
LG Electronics Inc. |
R4-2008753 |
CR for correction of Angle of Arrival for Radiated Requirements in section 4 |
LG Electronics Inc. |
4.11.2 |
UE demodulation and CSI (38.101-4) [NR_newRAT-Perf] |
|
R4-2006069 |
CR to Aperiodic Report Slot Offset for CQI report |
ANRITSU LTD |
R4-2006070 |
CR to Aperiodic Report Slot Offset for CQI report |
ANRITSU LTD |
R4-2006134 |
CR on DL Physical Channel EPRE Ratios |
Qualcomm Incorporated |
R4-2006523 |
Discussion on DL physical channels power ratios |
Intel Corporation |
R4-2006524 |
CR to TS 38.101-4: Beamforming clarification (R15) |
Intel Corporation |
R4-2006525 |
CR to TS 38.101-4: Beamforming clarification (R16) |
Intel Corporation |
R4-2006541 |
CR to TS 38.101-4: MIMO correlation matrices definition (R15) |
Intel Corporation |
R4-2006542 |
CR to TS 38.101-4: MIMO correlation matrices definition (R16) |
Intel Corporation |
R4-2006959 |
Update of DL physical channels definitions |
Rohde & Schwarz |
R4-2007226 |
CR: updates to NR CSI test |
Huawei, HiSilicon |
R4-2007227 |
Discussion on DL channel mapping for NR UE performance tests |
Huawei, HiSilicon |
R4-2007228 |
CR: clarification on EPRE ratio definition |
Huawei, HiSilicon |
R4-2008749 |
CR to TS 38.101-4: Beamforming clarification (R15) |
Intel Corporation |
R4-2008750 |
Update of DL physical channels definitions |
Rohde & Schwarz |
R4-2008751 |
CR: clarification on EPRE ratio definition |
Huawei, HiSilicon |
R4-2008752 |
CR to TS 38.101-4: MIMO correlation matrices definition (R15) |
Intel Corporation |
R4-2008754 |
CR: updates to NR CSI test |
Huawei, HiSilicon |
R4-2009059 |
Update of DL physical channels definitions |
Rohde & Schwarz |
R4-2009060 |
CR: clarification on EPRE ratio definition |
Huawei, HiSilicon |
4.11.3 |
BS demodulation (38.104) [NR_newRAT-Perf] |
|
R4-2006048 |
CR for 38.104: Performance requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 |
Nokia, Nokia Shanghai Bell |
R4-2006049 |
CR for 38.141-2: Radiated test requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 |
Nokia, Nokia Shanghai Bell |
R4-2006050 |
CR for 38.104: Performance requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 |
Nokia, Nokia Shanghai Bell |
R4-2006051 |
CR for 38.141-2: Radiated test requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 |
Nokia, Nokia Shanghai Bell |
R4-2006838 |
UCI multiplexed on PUSCH requirement |
Ericsson |
R4-2007461 |
CR to 38.104: Adding missing clause on Radiated Performance requirements for multi-slot PUCCH (11.3.1) |
Keysight Technologies UK Ltd |
R4-2007462 |
CR to 38.104: Adding missing clause on Radiated Performance requirements for multi-slot PUCCH (11.3.1) |
Keysight Technologies UK Ltd |
R4-2007463 |
CR to 38.141-1: Adding missing TT value for BS demod testing (C.3) |
Keysight Technologies UK Ltd |
R4-2007464 |
CR to 38.141-1: Adding missing TT value for BS demod testing (C.3) |
Keysight Technologies UK Ltd |
R4-2007465 |
CR to 38.141-2: Correction on required SNR value for multi-slot PUCCH testing (8.3.6) (C.3) |
Keysight Technologies UK Ltd |
R4-2007466 |
CR to 38.141-2: Correction on required SNR value for multi-slot PUCCH testing (8.3.6) (C.3) |
Keysight Technologies UK Ltd |
R4-2008870 |
UCI multiplexed on PUSCH requirement |
Ericsson |
4.12 |
Maintenance of the Positioning specs (36.171, 37.171 and 38.171) [NR_newRAT-Perf or TEI] |
|
R4-2006243 |
CR for TS36.171, Introduction of BDS B1C in A-GNSS |
CATT |
R4-2006244 |
CR for TS38.171, Introduction of BDS B1C in A-GNSS |
CATT |
R4-2008492 |
Email discussion summary for [95e][203] NR_NewRAT_Positioning |
Moderator (Spirent) |
R4-2008540 |
CR for TS38.171, Introduction of BDS B1C in A-GNSS |
CATT |
R4-2008551 |
CR for TS36.171, Introduction of BDS B1C in A-GNSS |
CATT |
R4-2009015 |
Email discussion summary for [95e][203] NR_NewRAT_Positioning |
Moderator (Spirent) |
4.13 |
Testability Maintenance (38.810) [FS_NR_test_methods] |
|
R4-2008014 |
Beam correspondence |
Keysight Technologies UK Ltd |
R4-2009049 |
Beam correspondence |
Keysight Technologies UK Ltd |
5 |
Rel-16 Work Items for LTE |
|
R4-2008296 |
Email discussion summary for [95e][106] LTE_Baskets |
Moderator (Ericsson) |
5.1.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R16_intra-Core/Perf] |
|
R4-2006044 |
TR 36.716-01-01 v0.9.0 Rel-16 LTE Intra-band |
Ericsson |
R4-2007596 |
Revised WID Basket WI for LTE Intra-band CA Rel-16 |
Ericsson |
R4-2007604 |
CR introduction of Rel-16 LTE Intra-band combinations in 36.101 |
Ericsson |
R4-2007635 |
CR Rel-16 for editorial corrections TS 36.101 |
Ericsson |
5.1.2 |
UE RF [LTE_CA_R16_intra-Core] |
|
R4-2006340 |
CR Coexistence cleanup for 36101 Rel15 |
Apple Inc. |
R4-2006341 |
CR Coexistence cleanup for 36101 Rel16 |
Apple Inc. |
R4-2006493 |
CA_48B A-MPR |
Nokia |
5.2.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R16_2BDL_1BUL-Core/Perf] |
|
R4-2007560 |
Revised WID: Rel16 LTE inter-band CA for 2 bands DL with 1 band UL |
Qualcomm Incorporated |
R4-2007561 |
Introduction of Rel-16 LTE inter-band CA for 2 bands DL with 1 band UL combinations in TS36101 |
Qualcomm Incorporated |
R4-2007562 |
TR 36.716-02-01-030 Rel-16 2 Bands DL and 1 Band UL CA |
Qualcomm Incorporated |
5.3.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R16_3BDL_1BUL-Core/Perf] |
|
R4-2008167 |
Introduction of completed R16 3DL band combinations to TS 36.101 |
Huawei, HiSilicon |
R4-2008169 |
Revised WID for LTE inter-band CA for 3 bands DL with 1 bands UL |
Huawei, HiSilicon |
5.3.3 |
UE RF without specific issues [LTE_CA_R16_3BDL_1BUL-Core] |
|
R4-2008210 |
TR 36.716-03-01 |
Huawei |
5.4.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R16_xBDL_1BUL-Core] |
|
R4-2006583 |
Introduction of LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL to TS36.101 |
Nokia, Nokia Shanghai Bell |
R4-2008059 |
Revised WI: Rel |
Nokia, Nokia Shanghai Bell |
5.5.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R16_2BDL_2BUL-Core] |
|
R4-2008233 |
Revised WID for LTE inter-band CA for 2 bands DL with 2 bands UL |
Huawei, HiSilicon |
R4-2008234 |
Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
Huawei, HiSilicon |
R4-2008235 |
TR 36.716-02-02 Rel-16_v0.6.0 |
Huawei, HiSilicon |
5.5.3 |
UE RF without specific issues [LTE_CA_R16_2BDL_2BUL-Core] |
|
R4-2006593 |
Draft CR: Correction to 2UL 2-14 and 14-30 |
Nokia, Nokia Shanghai Bell |
R4-2006594 |
Draft CR: Inclusion of 2UL CA_14-66 to CA_14-66-66 and CA_14-66-66-66 |
Nokia, Nokia Shanghai Bell |
5.6.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R16_xBDL_2BUL-Core] |
|
R4-2006723 |
TR 36.716-03-02 v1.0.0 LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-16 |
LG Electronics France |
R4-2006724 |
Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-16 |
LG Electronics France |
R4-2006725 |
Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL to TS36.101 |
LG Electronics France |
5.6.2 |
UE RF with MSD [LTE_CA_R16_xBDL_2BUL-Core] |
|
R4-2006597 |
TP to TR 36.716-03-02 on 3DL/2UL CA_2-14-66 |
Nokia, Nokia Shanghai Bell |
R4-2006598 |
TP to TR 36.716-03-02 on 4DL/2UL CA_2-14-30-66 |
Nokia, Nokia Shanghai Bell |
R4-2006792 |
TP on summary of self-interference analysis for new x bands (x=3,4,5) DL with 2 bands UL |
LG Electronics Polska |
R4-2008333 |
TP to TR 36.716-03-02 on 3DL/2UL CA_2-14-66 |
Nokia, Nokia Shanghai Bell |
R4-2008334 |
TP to TR 36.716-03-02 on 4DL/2UL CA_2-14-30-66 |
Nokia, Nokia Shanghai Bell |
5.6.3 |
UE RF without MSD [LTE_CA_R16_xBDL_2BUL-Core] |
|
R4-2006595 |
TP to TR 36.716-03-02 on 3DL/2UL CA_2-14-30 |
Nokia, Nokia Shanghai Bell |
R4-2006596 |
TP to TR 36.716-03-02 on 3DL/2UL CA_14-30-66 |
Nokia, Nokia Shanghai Bell |
R4-2008331 |
TP to TR 36.716-03-02 on 3DL/2UL CA_2-14-30 |
Nokia, Nokia Shanghai Bell |
R4-2008332 |
TP to TR 36.716-03-02 on 3DL/2UL CA_14-30-66 |
Nokia, Nokia Shanghai Bell |
5.8.2 |
Others [LTE_bands_R16_M1_NB1-Perf] |
|
R4-2007335 |
Adding UE category NB1 supporting LTE band 42/43 |
Huawei, HiSilicon |
5.10.1 |
General [LTE_eMTC5] |
|
R4-2008297 |
Email discussion summary for [95e][107] LTE_eMTC5_IOTenh3 |
Moderator (Huawei) |
R4-2008937 |
Email discussion summary for [95e][107] LTE_eMTC5_IOTenh3 |
Moderator (Huawei) |
5.10.2 |
Coexistence with NR [LTE_eMTC5] |
|
R4-2007115 |
TP for TR 37.823: Power boosting for LTE-MTC |
Nokia, Nokia Shanghai Bell |
R4-2007586 |
TP to 37.823: Conclusion |
Ericsson |
R4-2008423 |
TP for TR 37.823: Power boosting for LTE-MTC |
Nokia, Nokia Shanghai Bell |
R4-2008424 |
TP to 37.823: Conclusion |
Ericsson |
5.10.3 |
RRM core requirements (36.133) [LTE_eMTC5-Core] |
|
R4-2008518 |
Email discussion summary for [95e][229] LTE_eMTC5_RRM |
Moderator (Ericsson) |
R4-2008641 |
WF on Rel-16 MTC RRM requirements |
Ericsson |
R4-2008642 |
LS on capability signaling for RSS neighbor cell measurements |
Qualcomm |
R4-2009091 |
Email discussion summary for [95e][229] LTE_eMTC5_RRM |
Moderator (Ericsson) |
5.10.3.1 |
DL quality report in MSG3 and connected mode [LTE_eMTC5-Core] |
|
R4-2006181 |
Corrections to DCQR in eMTC and introduction of 2-bit DCQR |
Qualcomm Incorporated |
R4-2007369 |
2-bit reporting table on eMTC DL quality report |
Ericsson |
R4-2007370 |
Introduction of DL channel quality report for eMTC |
Ericsson |
R4-2007870 |
Discussion on quality reporting in Rel-16 eMTC |
Huawei, HiSilicon |
R4-2007871 |
CR on for quality reporting |
Huawei, HiSilicon |
R4-2008648 |
Introduction of DL channel quality report for eMTC |
Ericsson |
5.10.3.3 |
MPDCCH performance improvement [LTE_eMTC5-Core] |
|
R4-2007367 |
RLM for enhanced MPDCCH |
Ericsson |
R4-2007368 |
Introduction of RLM requirements with enhanced MPDCCH |
Ericsson |
R4-2008647 |
Introduction of RLM requirements with enhanced MPDCCH |
Ericsson |
5.10.3.4 |
PUR [LTE_eMTC5-Core] |
|
R4-2006164 |
Remaining issues in PUR for eMTC |
Qualcomm Incorporated |
R4-2007872 |
Discussion on capturing RRM requirements for PUR in Rel-16 eMTC |
Huawei, HiSilicon |
R4-2007873 |
CR to add additional timing requirements for PUR |
Huawei, HiSilicon |
R4-2007874 |
CR on RRM requirements for PUR |
Huawei, HiSilicon |
R4-2007883 |
Overview of the PUR agreements for Rel-16 MTC |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007884 |
Introduction of requirements for preconfigured uplink resource transmission for cat-M1 |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2007919 |
Introduction of requirements for preconfigured uplink resource transmission for cat-M1 |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2008645 |
Introduction of requirements for preconfigured uplink resource transmission for cat-M1 |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2008646 |
CR to add additional timing requirements for PUR |
Huawei, HiSilicon |
R4-2009137 |
Introduction of requirements for preconfigured uplink resource transmission for cat-M1 |
Ericsson, Nokia, Nokia Shanghai Bell |
5.10.3.5 |
Mobility enhancement [LTE_eMTC5-Core] |
|
R4-2006165 |
Remaining issues on RSS-based measurements in eMTC |
Qualcomm Incorporated |
R4-2007875 |
Discussion on remaining issues in RSS measurement |
Huawei, HiSilicon |
R4-2007885 |
Remaining discussions on RSS measurement support for Rel-16 MTC |
Ericsson |
R4-2007886 |
RSS based RSRP measurement to IDLE mode for eMTC in normal coverage |
Ericsson |
R4-2007887 |
RSS based RSRP measurement to IDLE mode for eMTC in enhanced coverage |
Ericsson |
R4-2007888 |
RSS based RSRP measurement to CONNECTED mode for eMTC |
Ericsson |
R4-2007889 |
Introduction of measurement accuracy requirements for RSS based RSRP measurements for cat-M1/M2 |
Ericsson |
R4-2008643 |
RSS based RSRP measurement to IDLE mode for eMTC in normal coverage |
Ericsson |
R4-2008644 |
RSS based RSRP measurement to IDLE mode for eMTC in enhanced coverage |
Ericsson |
R4-2009117 |
RSS based RSRP measurement to CONNECTED mode for eMTC |
Ericsson |
5.10.4 |
Demodulation and CSI requirements (36.101/36.104) [LTE_eMTC5-Perf] |
|
R4-2007111 |
UE and BS demodulation requirements for LTE_eMTC5 |
Nokia, Nokia Shanghai Bell |
R4-2007208 |
Discussion on multi-TB requirements for LTE eMTC |
Huawei, HiSilicon |
R4-2007209 |
Discussion and simulation reuslts for MPDCCH |
Huawei, HiSilicon |
R4-2007210 |
Discussion and simulation results for PMI reporting test in eMTC |
Huawei, HiSilicon |
R4-2007371 |
Simulation results of MPDCCH with DMRS+CRS |
Ericsson |
R4-2007372 |
Simulation results of CSI-RS based PMI reporting test |
Ericsson |
R4-2007373 |
Remaining open issues on eMTC demodulation requirements |
Ericsson |
R4-2007374 |
Introduction of enhanced MPDCCH demodulation requirements |
Ericsson |
R4-2007375 |
Introduction of CSI-RS based PMI reporting test for non-BL UEs |
Ericsson |
R4-2007376 |
Summary of simulation results for Rel-16 eMTC demodulation requirements |
Ericsson |
R4-2008702 |
Email discussion summary for [95e][313] LTE_eMTC5_Demod |
Moderator (Ericsson) |
R4-2008758 |
Way forward on UE/BS demodulation performance for additional MTC enhancements for LTE |
Ericsson |
R4-2008877 |
Email discussion summary for [95e][313] LTE_eMTC5_Demod |
Moderator (Ericsson) |
5.11.2 |
Coexistence with NR [NB_IOTenh3] |
|
R4-2006103 |
CR to TS 37.141: Correction on optional support of NB-IoT operation in NR in-band with CS17 |
Nokia, Nokia Shanghai Bell |
R4-2006104 |
CR to TS 37.141: Clarifications on test configurations for NB-IoT operation in NR in-band |
Nokia, Nokia Shanghai Bell |
R4-2008425 |
CR to TS 37.141: Clarifications on test configurations for NB-IoT operation in NR in-band |
Nokia, Nokia Shanghai Bell |
5.11.3 |
RRM core requirements (36.133) [NB_IOTenh3-Core] |
|
R4-2008519 |
Email discussion summary for [95e][230] NB_IOTenh3_RRM |
Moderator (Huawei, HiSilicon) |
R4-2008649 |
WF on Rel-16 NB-IoT RRM requirements |
Huawei, HiSilicon |
R4-2009092 |
Email discussion summary for [95e][230] NB_IOTenh3_RRM |
Moderator (Huawei, HiSilicon) |
R4-2009242 |
WF on Rel-16 NB-IoT RRM requirements |
Huawei, HiSilicon |
5.11.3.2 |
PUR [NB_IOTenh3-Core] |
|
R4-2007688 |
CR on measurement requriements for RSRP change based TA validation |
Huawei, Hisilicon |
R4-2008650 |
CR on measurement requriements for RSRP change based TA validation |
Huawei, Hisilicon |
R4-2009243 |
CR on measurement requriements for RSRP change based TA validation |
Huawei, Hisilicon |
5.11.3.3 |
Multi-carrier operations [NB_IOTenh3-Core] |
|
R4-2006166 |
Remaining issues on RRM measurements in non-anchor carrier for NB-IoT |
Qualcomm Incorporated |
R4-2007113 |
On NRSRP processing in multicarrier operation |
Nokia, Nokia Shanghai Bell |
R4-2007685 |
CR on downlink channel quality measurement requirement for Rel-16 NB IoT |
Huawei, Hisilicon |
R4-2007686 |
CR on non-anchor RRM measurement requirements in enhanced coverage for Rel-16 NB IoT |
Huawei, Hisilicon |
R4-2007687 |
CR on non-anchor RRM measurement requirements in normal coverage for Rel-16 NB IoT |
Huawei, Hisilicon |
R4-2007690 |
Discussion on filtering of samples between carriers for Rel-16 NB-IoT |
Huawei, Hisilicon |
R4-2007890 |
Changes on the S criterion for non-anchor carrier measurements in enhanced coverage for Rel-16 NB IoT |
Ericsson |
R4-2007891 |
Changes on the S criterion for non-anchor carrier measurements in normal coverage for Rel-16 NB IoT |
Ericsson |
R4-2007976 |
Changes on the S criterion for non-anchor carrier measurements in enhanced coverage for Rel-16 NB IoT |
Ericsson |
R4-2007977 |
Changes on the S criterion for non-anchor carrier measurements in normal coverage for Rel-16 NB IoT |
Ericsson |
R4-2008651 |
CR on non-anchor RRM measurement requirements in enhanced coverage for Rel-16 NB IoT |
Huawei, Hisilicon |
R4-2008652 |
CR on non-anchor RRM measurement requirements in normal coverage for Rel-16 NB IoT |
Huawei, Hisilicon |
R4-2008654 |
Changes on the S criterion for non-anchor carrier measurements in enhanced coverage for Rel-16 NB IoT |
Ericsson |
R4-2009241 |
CR on non-anchor RRM measurement requirements in normal coverage for Rel-16 NB IoT |
Huawei, Hisilicon |
5.11.3.4 |
Others [NB_IOTenh3-Core] |
|
R4-2006167 |
On shorter DRX cycles for NB-IoT |
Qualcomm Incorporated |
R4-2007114 |
NTA_offset setting for NR coexistence with NB-IoT |
Nokia, Nokia Shanghai Bell, Ericsson |
R4-2007689 |
CR on updating RRM requirement for new introduced UE specific DRX cycles for Rel-16 NB-IoT |
Huawei, Hisilicon |
R4-2007691 |
Discussion on updating RRM requirement for new introduced UE specific DRX cycles for Rel-16 NB-IoT |
Huawei, Hisilicon |
R4-2008653 |
CR on updating RRM requirement for new introduced UE specific DRX cycles for Rel-16 NB-IoT |
Huawei, Hisilicon |
5.11.4 |
Demodulation and CSI requirements (36.101/36.104) [NB_IOTenh3-Perf] |
|
R4-2007112 |
UE and BS demodulation requirements for NB_IOTenh3 |
Nokia, Nokia Shanghai Bell |
R4-2007211 |
Discussion on NPDSCH performance requirements for NB-IoT additional enhancements |
Huawei, HiSilicon |
R4-2007212 |
Discussion on NPUSCH format 1 performance requirements for NB-IoT additional enhancements |
Huawei, HiSilicon |
R4-2007377 |
NPDSCH/NPUSCH demodulation requirements with multi-TB transmission |
Ericsson |
R4-2008703 |
Email discussion summary for [95e][314] NB_IOTenh3_Demod |
Moderator (Huawei) |
R4-2008759 |
WF on LTE UE and BS performance requirements for additional enhancements of NB-IoT |
Huawei, HiSilicon |
R4-2008878 |
Email discussion summary for [95e][314] NB_IOTenh3_Demod |
Moderator (Huawei) |
5.12.1 |
RRM core requirements (36.133) [LTE_feMob-Core] |
|
R4-2008520 |
Email discussion summary for [95e][231] LTE_feMob_RRM |
Moderator (Nokia) |
R4-2008655 |
WF on test cases for LTE feMob |
Nokia |
R4-2009093 |
Email discussion summary for [95e][231] LTE_feMob_RRM |
Moderator (Nokia) |
R4-2009135 |
WF on test cases for LTE feMob |
Nokia |
5.12.1.1 |
Conditional handover [LTE_feMob-Core] |
|
R4-2008193 |
CR on 36133 LTE CHO |
Nokia, Nokia Shanghai Bell |
5.12.1.2 |
Reduction of user data interruption [LTE_feMob-Core] |
|
R4-2006981 |
Sync side conditions for LTE DAPS handover |
Ericsson |
R4-2006982 |
Correction to DAPS HO requirements in 36.133 |
Ericsson |
R4-2007750 |
CR on DAPS handover |
Huawei, Hisilicon |
R4-2009110 |
CR on DAPS handover |
Huawei, Hisilicon |
R4-2009259 |
CR on DAPS handover |
Huawei, Hisilicon |
5.13.1 |
Demodulation and CSI requirements (36.101) [LTE_terr_bcast -Perf] |
|
R4-2006720 |
5G broadcast simulation results collection |
Qualcomm, Inc. |
R4-2006721 |
On LTE-based 5G terrestrial broadcast demod requirement applicatioin rule |
Qualcomm, Inc. |
R4-2006722 |
CR: 5G broadcast demod requirement |
Qualcomm, Inc. |
R4-2007239 |
Discussion and simulation results on UE performance requirements for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2007240 |
CR addition on FRC and propagation conditions definition for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2007241 |
CR addition on performance requirements for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2008284 |
CR addition on FRC and propagation conditions definition for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2008285 |
CR addition on performance requirements for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2008704 |
Email discussion summary for [95e][315] LTE_terr_bcast_Demod |
Moderator (Qualcomm) |
R4-2008760 |
CR addition on performance requirements for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2008761 |
Summary of alignment and impairment results for 5G broadcast |
Qualcomm |
R4-2008879 |
Email discussion summary for [95e][315] LTE_terr_bcast_Demod |
Moderator (Qualcomm) |
5.13.2 |
Others [LTE_terr_bcast -Core/Perf] |
|
R4-2007396 |
Impacts on BS RF requirement of new introduced numerology |
ZTE Corporation |
R4-2007397 |
CR to 36.104: Introduction of LTE based 5G terrestrial broadcast numerologies |
ZTE Corporation |
R4-2007398 |
CR to 36.101: Introduction of LTE based 5G terrestrial broadcast numerologies |
ZTE Corporation |
R4-2008869 |
WF on the measurement interval and observation time for frequency/time correction for 2.5kHz and 0.37kHz |
ZTE |
5.14.1 |
RF [WI code] |
|
R4-2006090 |
Regulatory updates for Band 24 |
Ligado Networks |
R4-2006750 |
Adding Band34 for UE category 1bis into Rel-16 TS 36.101 |
CMCC |
R4-2006751 |
CR for REL-16 TS36.307 for adding B34 to UE category 1bis |
CMCC |
R4-2008298 |
Email discussion summary for [95e][108] LTE_Maintenance |
Moderator (Skyworks) |
R4-2008426 |
CR for REL-16 TS36.307 for adding B34 to UE category 1bis |
CMCC |
R4-2008938 |
Email discussion summary for [95e][108] LTE_Maintenance |
Moderator (Skyworks) |
5.14.3 |
Demodulation and CSI requirements [WI code] |
|
R4-2007178 |
CR to TS 36.104 Finalization on PUSCH performance requirements for enhanced HST scenario |
NTT DOCOMO, INC. |
R4-2007179 |
CR to TS 36.141 Finalization on PUSCH performance requirements for enhanced HST scenario |
NTT DOCOMO, INC. |
R4-2007180 |
CR to TS 36.104 Finalization on PRACH performance requirements for enhanced HST scenario |
NTT DOCOMO, INC. |
R4-2007181 |
CR to TS 36.141 Finalization on PRACH performance requirements for enhanced HST scenario |
NTT DOCOMO, INC. |
6.1.1 |
System Parameters [NR_unlic-Core] |
|
R4-2006141 |
NR-U Punctured Channel SEM for 100 MHz Bandwidth |
CableLabs |
R4-2006333 |
On introduction of 6GHz band for NR-U |
Apple Inc. |
R4-2006334 |
NR-U bandwidth classes and wideband operation |
Apple Inc. |
R4-2006335 |
In-carrier guard bands and wideband operation for 60kHz SCS |
Apple Inc. |
R4-2006568 |
On NR-U intra-carrier guardband for 60 kHz |
Intel Corporation |
R4-2007175 |
NR-U - Wideband operation and Intra-Carrier Guardbands |
Nokia, Nokia Shanghai Bell |
R4-2007321 |
Further considerations of spectrum utilization for NR-U |
Huawei, HiSilicon |
R4-2007322 |
Further considerations on guard band on wideband operation |
Huawei, HiSilicon |
R4-2007323 |
Considerations on 100MHz CBW in NR-U |
Huawei, HiSilicon |
R4-2007417 |
Discussion on 100MHz for NR-U |
ZTE Corporation |
R4-2007482 |
Discussion on 6 GHz NR-U band details |
Nokia, Nokia Shanghai Bell, AT&T |
R4-2008123 |
NR-U 6 GHz Bands n96 and n97 |
Qualcomm Incorporated |
R4-2008299 |
Email discussion summary for [95e][109] NR_unlic_SysParameters |
Moderator (Ericsson) |
R4-2008427 |
WF on band definition and corresponding requirements in 6GHz for Rel-16 NR-U |
Qualcomm |
R4-2008428 |
Draft CR on Guardband design for NR-U |
Nokia |
R4-2008429 |
WF on 100MHz CBW in NR-U |
Huawei |
R4-2008430 |
Draft CR on Introduction of NR-U CA combinations in Rel-16 |
Charter, T-Mobile USA |
R4-2008431 |
Draft CR on Introduction of NR-U EN-DC combinations in Rel-16 |
Charter, T-Mobile USA, Ericsson |
R4-2008433 |
WF on wideband operations for Rel-16 NR-U |
Apple |
R4-2008939 |
Email discussion summary for [95e][109] NR_unlic_SysParameters |
Moderator (Ericsson) |
R4-2009154 |
Draft CR on Introduction of NR-U CA combinations in Rel-16 |
Charter, T-Mobile USA, Ericsson |
6.1.2 |
UE RF requirements [NR_unlic-Core] |
|
R4-2008126 |
Introduction of NR-based access to unlicensed spectrum |
Qualcomm Incorporated |
R4-2008300 |
Email discussion summary for [95e][110] NR_unlic_UE_RF |
Moderator (Qualcomm) |
R4-2008434 |
WF on NR-U PC3 ACLR and in-band emissions |
Huawei |
R4-2008435 |
WF on NR-U ACS and blocking requirements |
Apple |
R4-2008436 |
WF on NR-U MPR |
MediaTek |
R4-2008437 |
Introduction of NR-based access to unlicensed spectrum |
Qualcomm Incorporated |
R4-2008940 |
Email discussion summary for [95e][110] NR_unlic_UE_RF |
Moderator (Qualcomm) |
R4-2009165 |
WF on NR-U PC3 ACLR and in-band emissions |
Huawei |
R4-2009175 |
Introduction of NR-based access to unlicensed spectrum |
Qualcomm Incorporated |
6.1.2.1 |
Transmitter characteristics [NR_unlic-Core] |
|
R4-2007044 |
Transmitter characeristics for n46 including initial simulations of required MPR and A-MPR for PC5 |
Ericsson |
R4-2007045 |
Introduction of TX characteristics for 5 GHz and 6 GHz shared channel access |
Ericsson |
R4-2007174 |
NR-U - Capturing Spectral Emission Mask in Specification |
Nokia, Nokia Shanghai Bell |
R4-2007319 |
Discussion on NR-U UE ACLR |
Huawei, HiSilicon |
R4-2007320 |
Considerations of in-band emissions for NR-U |
Huawei, HiSilicon |
R4-2008124 |
NR-U In-band emissions requirement |
Qualcomm Incorporated |
R4-2008125 |
NR-U MPR for PC5 single carrier and wideband |
Qualcomm Incorporated |
R4-2008127 |
NR-U A-MPR for Band n46 |
Qualcomm Incorporated |
R4-2008132 |
[NR-U] PC5 and PC3 Back-Off Measurements |
Skyworks Solutions Inc. |
R4-2008438 |
NR-U - Capturing Spectral Emission Mask in Specification |
Nokia, Nokia Shanghai Bell |
6.1.2.2 |
Receiver characteristics [NR_unlic-Core] |
|
R4-2006569 |
On NR-U UE ACS |
Intel Corporation |
R4-2006630 |
ACS, In-band and Out-of-band Blocking requirement for NR-U |
Apple Inc. |
R4-2006827 |
NR-U UE ACS and in-band blocking requirements for CA |
MediaTek Inc. |
R4-2007046 |
UE RF receiver characteristics for n46 for SA and NSA |
Ericsson |
R4-2007047 |
Introduction of RX characteristics for 5 GHz and 6 GHz shared channel access |
Ericsson |
R4-2007318 |
Discussion on NR-U UE ACS |
Huawei, HiSilicon |
R4-2008122 |
NR-U receiver ACS and blocking |
Qualcomm Incorporated |
6.1.3 |
Band combination related (Analysis, TPs, etc.) [NR_unlic-Core] |
|
R4-2006464 |
[DC] TP for TR 37.716-11-11 for DC_48_n46 |
Charter Communications, Inc |
R4-2006481 |
TP for TR 38.716-02-00 for CA_n48-n46 |
Charter Communications, Inc |
R4-2007107 |
Draft CR on Introduction of standalone NR-U combinations in Rel-16 |
Ericsson |
R4-2007108 |
TP on Inclusion of NR-U standalone combinations in TR 38 716-01-01: |
Ericsson |
R4-2007610 |
TP for TR 37.716-11-11 to correct MSD for DC_2_n46 |
Ericsson, T-Mobile US, MediaTek |
R4-2007918 |
TP for TR 38.716-02-00 to correct MSD for CA_n25-n46 |
Ericsson, T-Mobile US, MediaTek |
R4-2008432 |
Draft CR on Introduction of standalone NR-U combinations in Rel-16 |
Ericsson |
R4-2008976 |
TP for TR 37.716-11-11 to correct MSD for DC_2_n46 |
Ericsson, T-Mobile US, MediaTek |
6.1.4 |
BS RF requirements [NR_unlic-Core] |
|
R4-2007414 |
CR to 25.104:Introduction of Band n46 in 25.104 |
ZTE Corporation |
R4-2007415 |
CR to 36.104:Introduction of Band n46 in 36.104 |
ZTE Corporation |
R4-2007416 |
CR to 37.104:Introduction of Band n46 in 37.104 |
ZTE Corporation |
R4-2007478 |
CR to TS 38.104: Introduction of NR-U in core specification |
Nokia, Nokia Shanghai Bell |
R4-2007479 |
CR to 37.107 with introduction of NR-U feature |
Nokia, Nokia Shanghai Bell |
R4-2007567 |
CR to TS 38.104: Introduction of NR-U in core specification |
Eicsson |
R4-2008694 |
Email discussion summary for [95e][305] NR_unlic_RF_BS |
Moderator (Nokia) |
R4-2008762 |
CR to TS 38.104: Introduction of NR-U in core specification |
Nokia, Nokia Shanghai Bell |
R4-2008763 |
CR to 36.104:Introduction of Band n46 in 36.104 |
ZTE Corporation |
R4-2008764 |
CR to 37.104:Introduction of Band n46 in 37.104 |
ZTE Corporation |
R4-2008765 |
CR to 37.107 with introduction of NR-U feature |
Nokia, Nokia Shanghai Bell |
R4-2008766 |
WF on NR-U BS OBUE |
ZTE |
R4-2008880 |
Email discussion summary for [95e][305] NR_unlic_RF_BS |
Moderator (Nokia) |
6.1.4.1 |
Transmitter characteristics [NR_unlic-Core] |
|
R4-2007411 |
NR-U BS UEM requirement |
ZTE Corporation |
R4-2007412 |
CR tO 38.104:Introduction of NR-U BS UEM requirement into TS38.104 |
ZTE Corporation |
R4-2007480 |
CR to TS 38.104 with BS NR-U operating band unwanted emissions |
Nokia, Nokia Shanghai Bell |
6.1.4.2 |
Receiver characteristics [NR_unlic-Core] |
|
R4-2007409 |
NR-U BS RX REFSENS and dynamic range requirement |
ZTE Corporation |
R4-2007410 |
NR-U BS RX ICS requirement |
ZTE Corporation |
R4-2007413 |
CR to 38.104:Introduction of NR-U BS RX requirement into TS38.104 |
ZTE Corporation |
R4-2007476 |
NR-U BS Dynamic range requirement |
Nokia, Nokia Shanghai Bell |
R4-2007477 |
NR-U BS REFSENS and ICS requirements |
Nokia, Nokia Shanghai Bell |
6.1.5 |
RRM core requirements (38.133) [NR_unlic-Core] |
|
R4-2008493 |
Email discussion summary for [95e][204] NR_unlic_RRM_1 |
Moderator (Ericsson) |
R4-2008494 |
Email discussion summary for [95e][205] NR_unlic_RRM_2 |
Moderator (MediaTek) |
R4-2008495 |
Email discussion summary for [95e][206] NR_unlic_RRM_3 |
Moderator (Nokia) |
R4-2008524 |
Email discussion summary for [95e][204] NR_unlic_RRM_1 |
Moderator (Ericsson) |
R4-2008552 |
WF on NR-U RRM Requirements (Part 1) |
Ericsson |
R4-2008553 |
Analysis of missing NR-U sections for TS 38.133 |
ZTE |
R4-2008554 |
Analysis of missing NR-U sections for TS 36.133 |
Ericsson |
R4-2008567 |
WF on NR-U RRM Requirements (Part 2) |
MediaTek |
R4-2008575 |
WF on NR-U RRM Requirements (Part 3) |
Nokia |
R4-2008576 |
LS on Clarification on UE behavior after receiving the MAC CE deactivation command for semi-persistent CSI reporting in NR-U |
RAN4 |
R4-2009016 |
Email discussion summary for [95e][204] NR_unlic_RRM_1 |
Moderator (Ericsson) |
R4-2009017 |
Email discussion summary for [95e][205] NR_unlic_RRM_2 |
Moderator (MediaTek) |
R4-2009018 |
Email discussion summary for [95e][206] NR_unlic_RRM_3 |
Moderator (Nokia) |
R4-2009249 |
WF on NR-U RRM Requirements (Part 3) |
Nokia |
R4-2009250 |
Email discussion summary for [95e][204] NR_unlic_RRM_1 |
Moderator (Ericsson) |
6.1.5.1 |
General (specification structure, etc) [NR_unlic-Core] |
|
R4-2006010 |
CR for spec structure to address NR-U in 38.133 v3 |
ZTE Corporation |
R4-2006011 |
Discussion on approaches to address NR-U in 38.133 v3 |
ZTE Corporation |
R4-2006976 |
Updates to general section for NR-U in 36.133 |
Ericsson |
R4-2006977 |
Updates to general section for NR-U in 38.133 |
Ericsson |
R4-2008012 |
On NR-U terminology |
Ericsson |
R4-2008555 |
CR for spec structure to address NR-U in 36.133 |
Ericsson |
R4-2008556 |
CR for spec structure to address NR-U in 38.133 v3 |
ZTE Corporation |
R4-2008557 |
Updates to general section for NR-U in 36.133 |
Ericsson |
R4-2008558 |
Updates to general section for NR-U in 38.133 |
Ericsson |
R4-2009251 |
Updates to general section for NR-U in 38.133 |
Ericsson |
R4-2009262 |
Updates to general section for NR-U in 38.133 |
Ericsson |
6.1.5.2 |
Cell re-selection [NR_unlic-Core] |
|
R4-2006152 |
Remaining issues on cell reselection in NR-U |
Qualcomm Incorporated |
R4-2007696 |
CR on introduction of RRC_IDLE state moblity requirements for NR-U |
Huawei, Hisilicon |
R4-2007697 |
CR on introduction of RRC_INACTIVE state moblity requirements for NR-U |
Huawei, Hisilicon |
R4-2007701 |
Discussion on cell reselection for NR-U |
Huawei, Hisilicon |
R4-2007894 |
Remaining discussions on IDLE mode cell re-selection requirements for NR-U |
Ericsson |
R4-2007895 |
UE behaviour after measurement failure due to LBT for RRC_IDLE state moblity requirements for NR-U |
Ericsson |
R4-2007896 |
UE behaviour after measurement failure due to LBT for RRC_IDLE state inter-RAT mobility requirements for NR-U |
Ericsson |
R4-2007978 |
UE behaviour after measurement failure due to LBT for RRC_IDLE state mobility requirements for NR-U |
Ericsson |
R4-2008568 |
CR on introduction of RRC_IDLE state moblity requirements for NR-U |
Huawei, Hisilicon |
R4-2008569 |
CR on introduction of RRC_INACTIVE state moblity requirements for NR-U |
Huawei, Hisilicon |
R4-2008570 |
UE behaviour after measurement failure due to LBT for RRC_IDLE state inter-RAT mobility requirements for NR-U |
Ericsson |
6.1.5.3 |
Handover [NR_unlic-Core] |
|
R4-2006153 |
Remaining issues in NR-U HO requirements |
Qualcomm Incorporated |
R4-2007259 |
CR to TS 36.133: adding handover to NR-U |
Nokia, Nokia Shanghai Bell |
R4-2007260 |
CR to TS 38.133: adding NR-U Handover. |
Nokia, Nokia Shanghai Bell |
R4-2007897 |
Remaining discussions on handover requirements for NR-U |
Ericsson |
R4-2007898 |
Removal of editor’s note in NR-U inter-RAT handover requirements |
Ericsson |
R4-2007899 |
Removal of Editor’s note in NR-U handover requirements |
Ericsson |
R4-2007979 |
Removal of editor |
Ericsson |
R4-2007980 |
Removal of Editor |
Ericsson |
R4-2008559 |
CR to TS 36.133: adding handover to NR-U |
Nokia, Nokia Shanghai Bell |
R4-2008560 |
CR to TS 38.133: adding NR-U Handover. |
Nokia, Nokia Shanghai Bell |
R4-2009138 |
CR to TS 38.133: adding NR-U Handover. |
Nokia, Nokia Shanghai Bell |
6.1.5.4 |
RRC connection mobility control [NR_unlic-Core] |
|
R4-2006009 |
UE behavior in RRC release with re-direction in NR-U |
ZTE Corporation |
R4-2006154 |
On RRC release with redirection in NR-U |
Qualcomm Incorporated |
R4-2006563 |
CR to TS 38.133: RRC re-establishment with CCA |
Intel Corporation |
R4-2007986 |
Further analysis of RRC re-establishment requirements in NR-U |
Ericsson |
R4-2007987 |
Further analysis of RRC release with redirection requirements in NR-U |
Ericsson |
R4-2007988 |
RRC release with redirection requirements in NR-U in 38.133 |
Ericsson |
R4-2007989 |
RRC release with redirection requirements in NR-U in 36.133 |
Ericsson |
R4-2008561 |
CR to TS 38.133: RRC re-establishment with CCA |
Intel Corporation |
R4-2008562 |
RRC release with redirection requirements in NR-U in 38.133 |
Ericsson |
R4-2008563 |
RRC release with redirection requirements in NR-U in 36.133 |
Ericsson |
6.1.5.5 |
SCell activation/deactivation (delay and interruption) [NR_unlic-Core] |
|
R4-2006155 |
On Scell activation and deactivation requirements in NR-U |
Qualcomm Incorporated |
R4-2006175 |
Introduction of activation and deactivation delay requirements for SCells operating with CCA |
Qualcomm Incorporated |
R4-2007968 |
On SCell activation delay in NR-U |
Ericsson |
R4-2008564 |
Introduction of activation and deactivation delay requirements for SCells operating with CCA |
Qualcomm Incorporated |
6.1.5.6 |
PSCell addition/release (delay and interruption) [NR_unlic-Core] |
|
R4-2006156 |
Remaining issues on PSCell addition and release in NR-U |
Qualcomm Incorporated |
R4-2006176 |
Introduction of addition and release of NR PSCell operating with CCA in EN-DC |
Qualcomm Incorporated |
R4-2007972 |
On PSCell addition in NR-U |
Ericsson |
R4-2008565 |
Introduction of addition and release of NR PSCell operating with CCA in EN-DC |
Qualcomm Incorporated |
R4-2009252 |
Introduction of addition and release of NR PSCell operating with CCA in EN-DC |
Qualcomm Incorporated |
6.1.5.7 |
Active TCI state switching [NR_unlic-Core] |
|
R4-2007143 |
TCI state switching under NR-U |
ZTE Corporation |
R4-2007694 |
CR on introduction of Active TCI state switching delay with CCA Requirements for NR-U |
Huawei, Hisilicon |
R4-2007704 |
Discussion on TCI state switch for NR-U |
Huawei, Hisilicon |
R4-2007969 |
On active TCI state switching requirements in NR-U |
Ericsson |
R4-2008280 |
TCI state switching under NR-U |
ZTE Corporation |
R4-2008566 |
CR on introduction of Active TCI state switching delay with CCA Requirements for NR-U |
Huawei, Hisilicon |
6.1.5.9 |
Active BWP switching [NR_unlic-Core] |
|
R4-2006012 |
On BWP switch in NR-U |
ZTE Corporation |
R4-2006157 |
Remaining issues on new UL BWP switching requirements in NR-U |
Qualcomm Incorporated |
R4-2007693 |
CR on introduction of Active BWP switching delay requirements for NR-U |
Huawei, Hisilicon |
R4-2007700 |
Discussion on Active BWP switch delay for NR-U |
Huawei, Hisilicon |
R4-2007983 |
Analysis of open issues in BWP switching requirement due to consistent UL failure |
Ericsson |
R4-2007984 |
BWP switching interruption requirement due to consistent UL failure in 38.133 |
Ericsson |
R4-2007985 |
Interruption due to BWP switching at consistent UL failure in 36.133 |
Ericsson |
R4-2008571 |
CR on introduction of Active BWP switching delay requirements for NR-U |
Huawei, Hisilicon |
6.1.5.10 |
RLM and link recovery procedures [NR_unlic-Core] |
|
R4-2006014 |
Discussion on RLM in NR-U |
ZTE Corporation |
R4-2006158 |
On RLM requirements in NR-U |
Qualcomm Incorporated |
R4-2006858 |
Discussion on RLM requirement for NR-U |
MediaTek inc. |
R4-2007263 |
CR to 38.133: clarification of RLM requirements |
Nokia, Nokia Shanghai Bell |
R4-2007264 |
Discussion on RLM requirements in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2007341 |
On RLM for NR-U |
OPPO |
R4-2007387 |
Beam management in NR-U |
Ericsson |
R4-2007388 |
CR: Introduction of link recovery requirements with CCA |
Ericsson |
R4-2007698 |
CR on removing candidate in RLM requirements in Rel-15 |
Huawei, Hisilicon |
R4-2007699 |
CR on removing candidate in RLM requirements in Rel-16 |
Huawei, Hisilicon |
R4-2007703 |
Discussion on RLM and link recovery for NR-U |
Huawei, Hisilicon |
R4-2007970 |
On RLM in NR-U |
Ericsson |
R4-2007971 |
Introduction of RLM requirements for NR-U |
Ericsson |
R4-2008572 |
CR: Introduction of link recovery requirements with CCA |
Ericsson |
R4-2008573 |
Introduction of RLM requirements for NR-U |
Ericsson |
6.1.5.11 |
Measurement requirements [NR_unlic-Core] |
|
R4-2006019 |
Discussion on inter-RAT SFTD measurement towards NR-U |
ZTE Corporation |
R4-2006020 |
CR to address NR-U in inter-RAT SFTD measurements in 36.133 |
ZTE Corporation |
R4-2006021 |
L1-RSRP measurement in NR-U |
ZTE Corporation |
R4-2006022 |
UE behaviour under successive UL LBT failures during event-triggered reporting |
ZTE Corporation |
R4-2006023 |
PBCH payload reading for SSB index identification in NR-U |
ZTE Corporation |
R4-2006025 |
CR to address NR-U in EN-DC SFTD measurements in 36.133 |
ZTE Corporation |
R4-2006026 |
Pending issues on cell detection and serving cell measurement under NR-U |
ZTE Corporation |
R4-2006159 |
Remaining issues on measurement requirements in NR-U |
Qualcomm Incorporated |
R4-2006160 |
On RSSI and CO measurements in NR-U |
Qualcomm Incorporated |
R4-2006182 |
Remaining issues on serving cell evaluation in RRC connected mode for NR-U |
Apple |
R4-2006859 |
Discussion on SFTD measurements towards NR-U with LBT |
MediaTek inc. |
R4-2006860 |
Discussion on Scheduling Restriction for NR-U |
MediaTek inc. |
R4-2006861 |
Discussion on RSSI measurement for NR-U |
MediaTek inc. |
R4-2007261 |
CR to TS 38.133: adding NR-U inter-frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2007262 |
CR to TS 36.133: adding inter-RAT NR-U measurements |
Nokia, Nokia Shanghai Bell |
R4-2007265 |
RSSI and Channel Occupancy Measurements in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2007266 |
SSB measurements in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2007267 |
On the impact of UL LBT failure in measurement reporting |
Nokia, Nokia Shanghai Bell |
R4-2007268 |
Discussion on L1-RSRP measurements in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2007389 |
L1-RSRP measurements in NR-U |
Ericsson |
R4-2007390 |
CR: Introduction of L1-RSRP measurement requirements with CCA |
Ericsson |
R4-2007692 |
CR on introduction of intra-frequency measurements requirements for NR-U |
Huawei, Hisilicon |
R4-2007702 |
Discussion on measurement requirements for NR-U |
Huawei, Hisilicon |
R4-2007967 |
On RSSI and channel occupancy measurement requirements |
Ericsson |
R4-2007973 |
On intra-frequency measurements in NR-U |
Ericsson |
R4-2007974 |
On inter-frequency measurements in NR-U |
Ericsson |
R4-2008011 |
On intra-frequency and inter-frequency measurements in NR-U |
Ericsson |
R4-2008577 |
CR to TS 38.133: adding NR-U inter-frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2008578 |
CR to TS 36.133: adding inter-RAT NR-U measurements |
Nokia, Nokia Shanghai Bell |
R4-2008580 |
CR: Introduction of L1-RSRP measurement requirements with CCA |
Ericsson |
R4-2008581 |
CR on introduction of intra-frequency measurements requirements for NR-U |
Huawei, Hisilicon |
R4-2009101 |
CR to address NR-U in inter-RAT SFTD measurements in 36.133 |
ZTE Corporation |
R4-2009102 |
CR to address NR-U in EN-DC SFTD measurements in 36.133 |
ZTE Corporation |
6.1.5.12 |
Measurement capability and reporting criteria [NR_unlic-Core] |
|
R4-2006161 |
On measurement capabilities and reporting criteria in NR-U |
Qualcomm Incorporated |
R4-2006183 |
CR on UE measurements capability and reporting criteria for NR-U |
Apple |
R4-2006775 |
On pending issues of reporting delay in NR-U |
ZTE Corporation |
R4-2007695 |
CR on introduction of reporting criteria for NR-U |
Huawei, Hisilicon |
R4-2007975 |
On measurement reporting criteria for NR-U |
Ericsson |
R4-2008579 |
CR on introduction of reporting criteria for NR-U |
Huawei, Hisilicon |
R4-2009255 |
CR on introduction of reporting criteria for NR-U |
Huawei, Hisilicon |
6.1.5.13 |
Timing [NR_unlic-Core] |
|
R4-2006013 |
on uplink transmit timing requirements for NR-U |
ZTE Corporation |
R4-2006162 |
Remaining issues in NR-U timing requirements |
Qualcomm Incorporated |
R4-2006862 |
Discussion on timing requirement for NR-U |
MediaTek inc. |
R4-2006863 |
CR for timing requirement for NR-U |
MediaTek inc. |
R4-2007094 |
On the timing reference cell adaptation under DL LBT failure in reference cell |
Ericsson |
R4-2007097 |
Draft CR on UE transmit timing accuracy and timing reference cell under DL LBT failure |
Ericsson |
R4-2008574 |
CR for timing requirement for NR-U |
MediaTek inc. |
6.1.5.14 |
Others [NR_unlic-Core] |
|
R4-2007787 |
On inter-RAT SFTD for NR-U |
Ericsson |
6.2 |
Cross Link Interference (CLI) handling and Remote Interference Management (RIM) for NR [NR_CLI_RIM] |
|
R4-2008496 |
Email discussion summary for [95e][207] NR_CLI_RIM_RRM |
Moderator (LGE) |
R4-2009019 |
Email discussion summary for [95e][207] NR_CLI_RIM_RRM |
Moderator (LGE) |
6.2.2 |
RRM core requirements maintenance (38.133) [NR_CLI_RIM-Core] |
|
R4-2007825 |
CR on CLI measurement requirements |
Huawei, HiSilicon |
6.2.3.1 |
CLI measurement accuracy [NR_CLI_RIM-Perf] |
|
R4-2007826 |
CR on CLI measurement performance requirements |
Huawei, HiSilicon |
R4-2008582 |
CR on CLI measurement performance requirements |
Huawei, HiSilicon |
6.2.3.2 |
Test cases [NR_CLI_RIM-Perf] |
|
R4-2006691 |
Discussion on test setup for FR2 |
LG Electronics Inc. |
R4-2006692 |
CR for event triggered reporting tests for CLI |
LG Electronics Inc. |
R4-2007827 |
Discussion on AoA setup for CLI test cases |
Huawei, HiSilicon |
R4-2007828 |
CR on test cases for SRS-RSRP measurement accuracy in FR1 |
Huawei, HiSilicon |
R4-2007829 |
CR on test cases for SRS-RSRP measurement accuracy in FR2 |
Huawei, HiSilicon |
R4-2007830 |
CR on test cases for CLI-RSSI measurement accuracy in FR1 |
Huawei, HiSilicon |
R4-2007831 |
CR on test cases for CLI-RSSI measurement accuracy in FR2 |
Huawei, HiSilicon |
R4-2008131 |
On choice of CLI test setup |
Qualcomm CDMA Technologies |
R4-2008583 |
CR on test cases for SRS-RSRP measurement accuracy in FR2 |
Huawei, HiSilicon |
R4-2008584 |
CR on test cases for CLI-RSSI measurement accuracy in FR2 |
Huawei, HiSilicon |
6.3 |
NR mobility enhancement [NR_Mob_enh] |
|
R4-2008497 |
Email discussion summary for [95e][208] NR_Mob_enh_RRM |
Moderator (Intel Corporation) |
R4-2008585 |
WF on MR Mobility Enhancements |
Intel |
R4-2009020 |
Email discussion summary for [95e][208] NR_Mob_enh_RRM |
Moderator (Intel Corporation) |
6.3.2.1 |
Handover with simultaneous Rx/Tx with source and target cells [NR_Mob_enh-Core] |
|
R4-2006163 |
Remaining issues on NR DAPS HO |
Qualcomm Incorporated |
R4-2006543 |
Discussion on remaining issues on DAPS handover |
Intel Corporation |
R4-2006544 |
CR to TS 38.133: DAPS handover RRM requirement |
Intel Corporation |
R4-2006545 |
Reply LS on simultaneous reception of DL signals in intra-frequency DAPS HO |
Intel Corporation |
R4-2006887 |
Discussion on dual active protocol stack handover |
MediaTek inc. |
R4-2006978 |
Sync side conditions for NR DAPS handover |
Ericsson |
R4-2006979 |
Correction to DAPS HO requirements in 38.133 |
Ericsson |
R4-2007287 |
Discussion on remaining open issues on DAPS handover |
NEC |
R4-2007759 |
Further discussion on remaining issues on DAPS handover |
Huawei, HiSilicon |
R4-2007760 |
CR on DAPS handover requirements |
Huawei, HiSilicon |
R4-2007761 |
Draft LS on UE capabilities on DAPS HO |
Huawei, HiSilicon |
R4-2008194 |
CR on 38133 NR DAPS handover |
Nokia, Nokia Shanghai Bell |
R4-2008586 |
Correction to DAPS HO requirements in 38.133 |
Ericsson |
6.3.2.2 |
Conditional handover [NR_Mob_enh-Core] |
|
R4-2006546 |
CR to TS 38.133: CHO RRM requirement |
Intel Corporation |
R4-2009123 |
CR to TS 38.133: CHO RRM requirement |
Intel Corporation |
6.3.2.3 |
Conditional PSCell addition/change [NR_Mob_enh-Core] |
|
R4-2007762 |
CR on conditional PSCell change requirements |
Huawei, HiSilicon |
6.3.2.4 |
Others [NR_Mob_enh-Core] |
|
R4-2006980 |
Testcases for LTE and NR mobility enhancements |
Ericsson |
6.4.1 |
General [5G_V2X_NRSL] |
|
R4-2006247 |
Discussion on TR/TS structures and common terminology for NR V2X UE |
CATT |
R4-2006745 |
TR update TR38.886 v1.0.0 |
LG Electronics France |
R4-2006747 |
CR on NR V2X UE RF requirements for single carrier in TS38.101-1 |
LG Electronics France |
R4-2007090 |
Further discussion on general TR/TS structure issue and terminology for NR V2X |
vivo |
R4-2008301 |
Email discussion summary for [95e][111] 5G_V2X_NRSL_UE_RF_TX |
Moderator (LG Electronics) |
R4-2008439 |
WF on A-MPR for PSSCH/PSCCH transmission |
LG Electronics |
R4-2008440 |
WF on A-MPR for simultaneous PSFCH transmission |
Huawei |
R4-2008441 |
WF on MPR/A-MPR for S-SSB transmission |
Qualcomm |
R4-2008446 |
WF on TR/TS structures and common terminology for NR V2X UE |
Vivo, Qualcomm |
R4-2008941 |
Email discussion summary for [95e][111] 5G_V2X_NRSL_UE_RF_TX |
Moderator (LG Electronics) |
R4-2009168 |
WF on WF on remaining issues for TS 38.101-1 and TS 38.101-3 for NR-V2X |
LG Electronics, Huawei, HiSilicon |
6.4.2 |
System parameters [5G_V2X_NRSL-Core] |
|
R4-2006260 |
Discussion on BS impact of NR V2X |
CATT |
R4-2006264 |
CR for TS38.104, Introduce BS impact of NR V2X |
CATT |
R4-2006757 |
Discussion on SL-Uu simultaneous transmission in a UE in licensed band in rel-16 |
LG Electronics France |
R4-2006762 |
Discussion the remaining issues for n79 NR-V2X |
CMCC |
R4-2007091 |
Revisions on the CR on NR V2X UE RF requirements for single carrier in TS38.101-1 |
vivo |
R4-2007092 |
Further discussion on the synchronization mechanism between SL and Uu in the same TDD licensed band |
vivo |
R4-2008200 |
TP on Switching Period for Indevice Coexistence |
Futurewei Technologies |
R4-2008220 |
On synchronization scenario for NR V2X in licensed band |
Huawei, HiSilicon |
R4-2008303 |
Email discussion summary for [95e][113] 5G_V2X_NRSL_SysParameters |
Moderator (vivo) |
R4-2008453 |
WF on remaining issues for NR V2X system parameters |
vivo |
R4-2008454 |
WF on BS impact of NR V2X |
CATT |
R4-2008455 |
TP on Switching Period for Indevice Coexistence |
Futurewei Technologies |
R4-2008456 |
Revisions on the CR on NR V2X UE RF requirements for single carrier in TS38.101-1 |
vivo |
R4-2008457 |
CR for TS38.104, Introduce BS impact of NR V2X |
CATT |
R4-2008943 |
Email discussion summary for [95e][113] 5G_V2X_NRSL_SysParameters |
Moderator (vivo) |
R4-2009166 |
WF on remaining issues for NR V2X system parameters |
vivo |
6.4.3 |
UE RF requirements [5G_V2X_NRSL-Core] |
|
R4-2006746 |
TP on remaining issues for NR V2X UE (Coexistence table to remove n47 ETSI requirements -30dBm/MHz, configured Tx power) |
LG Electronics France |
R4-2008442 |
TP on remaining issues for NR V2X UE (Coexistence table to remove n47 ETSI requirements -30dBm/MHz, configured Tx power) |
LG Electronics France |
R4-2009149 |
TP on remaining issues for NR V2X UE (Coexistence table to remove n47 ETSI requirements -30dBm/MHz, configured Tx power) |
LG Electronics France |
6.4.3.1 |
Transmitter characteristics [5G_V2X_NRSL-Core] |
|
R4-2006701 |
TP on NR V2X A-MPR for PSSCH/PSCCH |
LG Electronics Inc. |
R4-2006758 |
Discussion on position of Switching period between LTE V2X and NR V2X at n47 |
LG Electronics France |
R4-2006818 |
TX diversity for NR-V2X |
Qualcomm Incorporated |
R4-2006820 |
TP on 5G V2X MPR A-MPR for S-SSB transmission |
Qualcomm Incorporated |
R4-2007880 |
TP to TR38.886 V2X PSSCH PSCCH A-MPR |
Qualcomm Austria RFFE GmbH |
R4-2007881 |
TP to TR38.886 A-MPR for 10 and 40MHz V2X PSFCH |
Qualcomm Incorporated |
R4-2008079 |
Discussion on ETSI NS issue, NS_33 AMPR and spurious emission for UE co-existence for V2X |
Huawei, HiSilicon |
R4-2008080 |
TP to update MPR\AMPR requirements for both PC3 and PC2 NR V2X in band n47 |
Huawei, HiSilicon |
R4-2008081 |
DraftCR to specify MPR\AMPR requirements for PC3 NR V2X in band n47 |
Huawei, HiSilicon |
R4-2008082 |
DraftCR to specify configured transmitted power for NR V2X in band n47 |
Huawei, HiSilicon |
R4-2008201 |
Simultaneous transmission of UL and SL in a licensed carrier |
Futurewei Technologies |
R4-2008203 |
Reply LS to RAN2 on UL-SL Prioritization |
Futurewei Technologies |
R4-2008443 |
DraftCR to specify MPR\AMPR requirements for PC3 NR V2X in band n47 |
Huawei, HiSilicon |
R4-2008444 |
DraftCR to specify configured transmitted power for NR V2X in band n47 |
Huawei, HiSilicon |
R4-2008445 |
TX diversity for NR-V2X |
Qualcomm Incorporated |
R4-2008447 |
Reply LS to RAN2 on UL-SL Prioritization |
Futurewei Technologies |
R4-2009150 |
Reply LS to RAN2 on UL-SL Prioritization |
RAN4 |
R4-2009163 |
DraftCR to specify MPR\AMPR requirements for PC3 NR V2X in band n47 |
Huawei, HiSilicon |
6.4.3.2 |
Receiver characteristics [5G_V2X_NRSL-Core] |
|
R4-2006259 |
Discussion on remaining issues on Rx RF requirements for NR V2X |
CATT |
R4-2006261 |
TP on remaining issues on Rx RF requirements for NR V2X |
CATT |
R4-2006262 |
CR for TS38.101-1, Introduce Rx RF requirements for NR V2X single carrier |
CATT |
R4-2006821 |
REFSENS issues in V2X |
Qualcomm Incorporated |
R4-2008223 |
On remaining NR V2X Rx requirements |
Huawei, HiSilicon |
R4-2008302 |
Email discussion summary for [95e][112] 5G_V2X_NRSL_UE_RF_RX |
Moderator (CATT) |
R4-2008448 |
WF on remaining Rx RF requirements for NR V2X |
CATT |
R4-2008449 |
TP on remaining issues on Rx RF requirements for NR V2X |
CATT |
R4-2008450 |
CR for TS38.101-1, Introduce Rx RF requirements for NR V2X single carrier |
CATT |
R4-2008942 |
Email discussion summary for [95e][112] 5G_V2X_NRSL_UE_RF_RX |
Moderator (CATT) |
R4-2009164 |
Email discussion summary for [95e][112] 5G_V2X_NRSL_UE_RF_RX |
Moderator (CATT) |
R4-2009170 |
WF on remaining Rx RF requirements for NR V2X |
CATT |
6.4.4 |
Concurrent operation (scenarios, requirements, etc) [5G_V2X_NRSL-Core] |
|
R4-2006248 |
Discussion on switching period in ITS band for NR V2X |
CATT |
R4-2006249 |
Discussion on con-current operation |
CATT |
R4-2006263 |
CR for TS38.101-1, Introduce Rx RF requirements for NR V2X con-current operation |
CATT |
R4-2006819 |
Switching time between NR SL and LTE SL |
Qualcomm Incorporated |
R4-2007093 |
Discussion on current operation scenario and clarification |
vivo |
R4-2007342 |
On switching period for LTE SL and NR SL |
OPPO |
R4-2008219 |
On switching period for LTE SL and NR SL |
Huawei, HiSilicon |
R4-2008221 |
On remaining issues of con-current operation |
Huawei, HiSilicon |
R4-2008222 |
CR for TS 38.101-3: NR V2X con-current operation |
Huawei, HiSilicon |
R4-2008304 |
Email discussion summary for [95e][114] 5G_V2X_NRSL_UE_Concurrent |
Moderator (Huawei) |
R4-2008451 |
WF on con-current operation remaining issues |
Huawei, HiSilicon |
R4-2008452 |
CR for TS 38.101-3: NR V2X con-current operation |
Huawei, HiSilicon |
R4-2008944 |
Email discussion summary for [95e][114] 5G_V2X_NRSL_UE_Concurrent |
Moderator (Huawei) |
R4-2009172 |
CR for TS 38.101-3: NR V2X con-current operation |
Huawei, HiSilicon |
6.4.5 |
RRM core requirements (38.133) [5G_V2X_NRSL-Core] |
|
R4-2006671 |
Discussion of remaining issues for NR V2X |
LG Electronics Inc. |
R4-2006709 |
CR of NR V2X editorial correction |
LG Electronics Inc. |
R4-2008498 |
Email discussion summary for [95e][209] 5G_V2X_NRSL_RRM_1 |
Moderator (LGE) |
R4-2008499 |
Email discussion summary for [95e][210] 5G_V2X_NRSL_RRM_2 |
Moderator (MediaTek) |
R4-2008587 |
WF on NR V2X RRM requirements |
LGE, MediaTek |
R4-2009021 |
Email discussion summary for [95e][209] 5G_V2X_NRSL_RRM_1 |
Moderator (LGE) |
R4-2009022 |
Email discussion summary for [95e][210] 5G_V2X_NRSL_RRM_2 |
Moderator (MediaTek) |
R4-2009109 |
CR of NR V2X editorial correction |
LG Electronics Inc. |
R4-2009275 |
CR of NR V2X editorial correction |
LG Electronics Inc. |
6.4.5.2 |
Synchronization requirements [5G_V2X_NRSL-Core] |
|
R4-2006674 |
Simulation results of PSBCH-RSRP measurement accuracy |
LG Electronics Inc. |
6.4.5.3 |
Measurement requirements [5G_V2X_NRSL-Core] |
|
R4-2006469 |
Discussion on NR V2X measurement requirement |
MediaTek inc. |
R4-2006470 |
CR on L1 SL-RSRP measurements |
MediaTek inc. |
R4-2006471 |
Link-level simulation for NR V2X PSBCH RSRP |
MediaTek inc. |
R4-2006685 |
CR of NR V2X measurement accuracy requirements(SL-RSSI and L1 SL-RSRP) |
LG Electronics Inc. |
R4-2006711 |
On NR V2X measurmeent requirement |
Qualcomm, Inc. |
R4-2007763 |
Simulation results of PSBCH-RSRP measurement accuracy |
Huawei, HiSilicon |
R4-2007764 |
Discussion on measurement related requirements for NR V2X |
Huawei, HiSilicon |
R4-2007765 |
CR on PSBCH-RSRP accuracy requirements for NR V2X |
Huawei, HiSilicon |
R4-2008592 |
CR on L1 SL-RSRP measurements |
MediaTek inc. |
R4-2008593 |
CR of NR V2X measurement accuracy requirements(SL-RSSI and L1 SL-RSRP) |
LG Electronics Inc. |
R4-2008594 |
CR on PSBCH-RSRP accuracy requirements for NR V2X |
Huawei, HiSilicon |
6.4.5.4 |
Interruption requirements [5G_V2X_NRSL-Core] |
|
R4-2006222 |
CR on interruption requirements for NR V2X |
CATT |
R4-2006472 |
Discussion on NR V2X interruption requirement |
MediaTek inc. |
R4-2006473 |
CR on V2X interruption |
MediaTek inc. |
R4-2006706 |
CR of interruption for switching between NR SL and LTE SL |
LG Electronics Inc. |
R4-2006712 |
On NR V2X interruption requirement |
Qualcomm, Inc. |
R4-2007766 |
Discussion on interruption related issues for NR V2X |
Huawei, HiSilicon |
R4-2008588 |
CR on interruption requirements for NR V2X |
CATT |
R4-2008589 |
CR of interruption for switching between NR SL and LTE SL |
LG Electronics Inc. |
6.4.5.5 |
Others [5G_V2X_NRSL-Core] |
|
R4-2006696 |
CR of NR V2X operating band group |
LG Electronics Inc. |
R4-2006700 |
CR of Annex.B for NR V2X side conditions |
LG Electronics Inc. |
R4-2006702 |
CR of NR V2X abbreviations |
LG Electronics Inc. |
R4-2008590 |
CR of NR V2X operating band group |
LG Electronics Inc. |
R4-2008591 |
CR of Annex.B for NR V2X side conditions |
LG Electronics Inc. |
6.5 |
Integrated Access and Backhaul for NR [NR_IAB] |
|
R4-2008695 |
Email discussion summary for [95e][306] NR_IAB_General |
Moderator (Huawei) |
R4-2008696 |
Email discussion summary for [95e][307] NR_IAB_Featurelist |
Moderator (CATT) |
R4-2008697 |
Email discussion summary for [95e][308] NR_IAB_RF_Part_1 |
Moderator (ZTE) |
R4-2008698 |
Email discussion summary for [95e][309] NR_IAB_RF_Part_2 |
Moderator (Nokia) |
R4-2008699 |
Email discussion summary for [95e][310] NR_IAB_RF_Part_3 |
Moderator (Samsung) |
R4-2008767 |
WF on IAB-MT class descriptions |
Huawei |
R4-2008768 |
TP to TR 38.809 – Correction of IAB-DU and IAB-MT permutation in subclause 4.8. |
Huawei |
R4-2008770 |
WF on referencing rules and how updated to donor specs are applied to the IAB specification |
Nokia |
R4-2008771 |
WF on IAB-MT feature list |
CATT |
R4-2008772 |
WF on IAB-MT supported channel bandwidth |
Samsung |
R4-2008773 |
WF on IAB-MT maximum output power and scaling factor for emission mask |
Ericsson |
R4-2008774 |
WF on IAB-MT Pc,max definition |
Samsung |
R4-2008775 |
WF on IAB-MT output power dynamic |
Qualcomm |
R4-2008783 |
WF on transmit signal quality |
CATT |
R4-2008784 |
WF on IAB-MT unwanted emissions |
Nokia, Nokia Shanghai Bell |
R4-2008785 |
WF on IAB-MT reference sensitivity |
Huawei |
R4-2008786 |
WF for In-band selectivity and blocking |
Ericsson |
R4-2008881 |
Email discussion summary for [95e][306] NR_IAB_General |
Moderator (Huawei) |
R4-2008882 |
Email discussion summary for [95e][307] NR_IAB_Featurelist |
Moderator (CATT) |
R4-2008883 |
Email discussion summary for [95e][308] NR_IAB_RF_Part_1 |
Moderator (ZTE) |
R4-2008884 |
Email discussion summary for [95e][309] NR_IAB_RF_Part_2 |
Moderator (Nokia) |
R4-2008885 |
Email discussion summary for [95e][310] NR_IAB_RF_Part_3 |
Moderator (Samsung) |
R4-2009051 |
LS on RAN4 IAB-MT feature list agreement |
RAN4 |
R4-2009065 |
WF on IAB-MT unwanted emissions |
Nokia, Nokia Shanghai Bell |
R4-2009066 |
WF for In-band selectivity and blocking |
Ericsson |
R4-2009067 |
WF on IAB-MT feature list |
CATT |
6.5.1 |
General [NR_IAB-Core] |
|
R4-2007467 |
Email discussion for updating IAB TS spec to capture RAN4 95 agreements |
Qualcomm |
R4-2009296 |
Email discussion for updating IAB TS spec to capture RAN4 95 agreements |
Qualcomm |
6.5.1.1 |
System parameters [NR_IAB-Core] |
|
R4-2006378 |
TR38.809 V0.2.0 |
Samsung |
R4-2007577 |
TP to TS 38.174: system parameter |
Ericsson |
R4-2008769 |
TP to TS 38.174: system parameter |
Ericsson |
6.5.1.2 |
IAB-MT class [NR_IAB-Core] |
|
R4-2007399 |
Discussion on IAB MT class |
ZTE Corporation |
R4-2007401 |
Further discussion on IAB-MT power requirement |
ZTE Corporation |
R4-2007903 |
IAB-MT class definitions |
Huawei |
6.5.1.3 |
IAB-MT feature list [NR_IAB-Core] |
|
R4-2006279 |
Discussion on IAB-MT Feature list |
CATT |
R4-2006657 |
Support of Rel-15 UE features by IAB-MTs |
AT&T |
R4-2006797 |
Further discussion on IAB-MT feature |
Samsung |
R4-2006798 |
Clarificaiton on IAB-MT channel bandwidth |
Samsung |
R4-2006803 |
On IAB feature list |
CMCC |
R4-2007119 |
IAB-MT features |
Nokia, Nokia Shanghai Bell |
R4-2007131 |
IAB-MT Tx Features |
Qualcomm Incorporated |
R4-2007317 |
Further discussion on R16 IAB MT RF features |
Huawei, HiSilicon |
R4-2007400 |
Discussion on IAB MT feature list |
ZTE Corporation |
R4-2007571 |
IAB-MT madatory feature |
Ericsson |
6.5.1.4 |
Others [NR_IAB-Core] |
|
R4-2006799 |
RAN4 implication due to Sync from multiple parenets for |
Samsung |
6.5.2.1.1 |
Transmitter characteristics [NR_IAB-Core] |
|
R4-2006276 |
Discussion on IAB-MT modulation quality requirements |
CATT |
R4-2006282 |
Discussion on IAB-MT power related issues |
CATT |
R4-2007402 |
frequency error requirement for IAB |
ZTE Corporation |
R4-2007403 |
Further discussion on FR1 IAB-MT ACLR and ACS requirement |
ZTE Corporation |
R4-2007543 |
[IAB RF] further discussion on IAB TX IMD |
ZTE Corporation |
R4-2007573 |
IAB-MT Frequency error |
Ericsson |
6.5.2.1.2 |
Receiver characteristics [NR_IAB-Core] |
|
R4-2006280 |
Discussion on IAB-MT REFSENS |
CATT |
R4-2007408 |
In-band blocking for IAB MT |
ZTE Corporation |
6.5.2.1.3 |
TP to TS/TR [NR_IAB-Core] |
|
R4-2006272 |
TP for TR 38.809: Transmit ON/OFF power |
CATT |
R4-2006273 |
TP for TS 38.174: Transmit ON/OFF power |
CATT |
R4-2006274 |
TP for TR 38.809: IAB-DU Transmitted signal quality |
CATT |
R4-2006275 |
TP for TS 38.174: IAB-DU Transmitted signal quality |
CATT |
R4-2006277 |
TP for TR 38.809: IAB-MT Transmitted signal quality |
CATT |
R4-2006278 |
TP for TS 38.174: IAB-MT Transmitted signal quality |
CATT |
R4-2007404 |
TP to TR : IAB RX IM requirement (section 8.7 and 10.8) |
ZTE Corporation |
R4-2007405 |
TP to TS 38.174: IAB RX IM requirement (section 7.7 and 10.8) |
ZTE Corporation |
R4-2007406 |
TP to TR: IAB ICS requirement (section 8.8 and 10.9) |
ZTE Corporation |
R4-2007407 |
TP to TS 38.174: IAB ICS requirement (section 7.8 and 10.9) |
ZTE Corporation |
R4-2007544 |
[IAB RF] TP to TR 38.809 IAB TX IMD |
ZTE Corporation |
R4-2007545 |
[IAB RF] TP to TS 38.174 IAB TX IMD |
ZTE Corporation |
R4-2007579 |
TP to TR 38.809: Conducted RX spurious |
Ericsson |
R4-2007585 |
TP to TS 38.174: Conducted RX spurious |
Ericsson |
R4-2008777 |
TP for TR 38.809: Transmit ON/OFF power |
CATT |
R4-2008778 |
TP for TS 38.174: Transmit ON/OFF power |
CATT |
R4-2008779 |
TP for TR 38.809: IAB-MT Transmitted signal quality |
CATT |
R4-2008780 |
TP for TS 38.174: IAB-MT Transmitted signal quality |
CATT |
R4-2008781 |
[IAB RF] TP to TS 38.174 IAB TX IMD |
ZTE Corporation |
R4-2008782 |
[IAB RF] TP to TR 38.809 IAB TX IMD |
ZTE Corporation |
R4-2008787 |
TP to TR : IAB RX IM requirement (section 8.7 and 10.8) |
ZTE Corporation |
R4-2008788 |
TP to TS 38.174: IAB RX IM requirement (section 7.7 and 10.8) |
ZTE Corporation |
R4-2008789 |
TP to TR: IAB ICS requirement (section 8.8 and 10.9) |
ZTE Corporation |
R4-2008791 |
TP to TS 38.174: IAB ICS requirement (section 7.8 and 10.9) |
ZTE Corporation |
R4-2008793 |
TP to TR 38.809: Conducted RX spurious |
Ericsson |
R4-2008799 |
TP to TS 38.174: Conducted RX spurious |
Ericsson |
R4-2009062 |
[IAB RF] TP to TR 38.809 IAB TX IMD |
ZTE Corporation |
6.5.2.2.1 |
Transmitter characteristics [NR_IAB-Core] |
|
R4-2006760 |
Discussion on IAB-MT dynamic range |
CMCC |
R4-2006800 |
Further discussion on IAB-MT transmitter requriement |
Samsung |
R4-2006931 |
IAB-MT Tx power dynamic range and power control requirements |
Nokia, Nokia Shanghai Bell |
R4-2007120 |
IAB-MT emission requirements |
Nokia, Nokia Shanghai Bell |
R4-2007121 |
TP to TS 38.174: Output power requirements |
Nokia, Nokia Shanghai Bell |
R4-2007122 |
TP to TR 38.809: Emission requirements |
Nokia, Nokia Shanghai Bell |
R4-2007130 |
IAB-MT Tx Requirements |
Qualcomm Incorporated |
R4-2007574 |
IAB-MT TX dynamic range and power control |
Ericsson |
R4-2007575 |
IAB-MT maximum output power |
Ericsson |
R4-2007576 |
IAB-MT unwanted emission for FR2 |
Ericsson |
R4-2007904 |
IAB-MT min number of TRX and emissions scaling |
Huawei |
R4-2007909 |
IAB-MT TX ACLR and dynamic range |
Huawei |
R4-2008776 |
TP to TS 38.174: Output power requirements |
Nokia, Nokia Shanghai Bell |
6.5.2.2.2 |
Receiver characteristics [NR_IAB-Core] |
|
R4-2006801 |
Further discussion on REFSENS for IAB-MT |
Samsung |
R4-2006932 |
IAB-MT blocking and selectivity requirements |
Nokia, Nokia Shanghai Bell |
R4-2007572 |
IAB-MT REFSENS |
Ericsson |
R4-2007900 |
IAB-MT LA FR2 Rx sensitivity requirement. |
Huawei |
R4-2007901 |
FR1 IAB-MT sensitivity |
Huawei |
R4-2007902 |
IAB-MT LA ACS and IBB |
Huawei |
6.5.2.2.3 |
TP to TS/TR [NR_IAB-Core] |
|
R4-2007578 |
TP to TR 38.809: OTA In-band blocking |
Ericsson |
R4-2007580 |
TP to TR 38.809: radiated RX spurious |
Ericsson |
R4-2007581 |
TP to TS 38.174: OTA ACS |
Ericsson |
R4-2007582 |
TP to TS 38.174: OTA RX spurious |
Ericsson |
R4-2007583 |
TP to TR 38.809: OTA ACS |
Ericsson |
R4-2007584 |
TP to TS 38.174: OTA Inband blocking |
Ericsson |
R4-2007905 |
TP to TS 38.174 -IAB-DU TX dynamic range |
Huawei |
R4-2007906 |
TP to TS 38.174 -IAB-MT TX dynamic range |
Huawei |
R4-2007907 |
TP to TS 38.174 -IAB-DU RX sensitivity |
Huawei |
R4-2007908 |
TP to TS 38.174 -IAB-DU Rx dynamic range |
Huawei |
R4-2008792 |
TP to TR 38.809: OTA In-band blocking |
Ericsson |
R4-2008794 |
TP to TR 38.809: radiated RX spurious |
Ericsson |
R4-2008795 |
TP to TS 38.174: OTA ACS |
Ericsson |
R4-2008796 |
TP to TS 38.174: OTA RX spurious |
Ericsson |
R4-2008797 |
TP to TR 38.809: OTA ACS |
Ericsson |
R4-2008798 |
TP to TS 38.174: OTA Inband blocking |
Ericsson |
R4-2008800 |
TP to TS 38.174 -IAB-DU RX sensitivity |
Huawei |
R4-2008801 |
TP to TS 38.174 -IAB-DU Rx dynamic range |
Huawei |
R4-2009063 |
TP to TS 38.174 -IAB-DU TX dynamic range |
Huawei |
6.5.3 |
RRM core requirements (38.133) [NR_IAB-Core] |
|
R4-2008500 |
Email discussion summary for [95e][211] NR_IAB_RRM |
Moderator (Qualcomm) |
R4-2008595 |
WF on NR IAB RRM requirements |
Qualcomm |
R4-2009023 |
Email discussion summary for [95e][211] NR_IAB_RRM |
Moderator (Qualcomm) |
6.5.3.1 |
General [NR_IAB-Core] |
|
R4-2007269 |
RRM requirements in IAB TR and TS |
ZTE Corporation |
R4-2007991 |
TP to TS 38.174 v0.0.1: Adding references related to IAB |
Ericsson |
R4-2008196 |
CR on 38174 RRM IAB TS |
Nokia, Nokia Shanghai Bell |
R4-2008238 |
CR on 38174 RRM IAB TS |
Nokia, Nokia Shanghai Bell |
R4-2008596 |
TP to 38174 RRM IAB TS |
Nokia, Nokia Shanghai Bell |
6.5.3.2 |
RRC connection mobility control [NR_IAB-Core] |
|
R4-2007189 |
Pending issues on RRC mobility control for IAB-MT |
ZTE Corporation |
R4-2007488 |
Discussion regarding RRC Connection Mobility Control in IAB Networks |
Qualcomm |
R4-2007489 |
TP for RRC Connection Mobility Control in IAB Networks |
Qualcomm |
R4-2007992 |
Handling 4 SMTC in RRC re-establishment and redirection for IAB MT |
Ericsson |
R4-2007993 |
TP to TS 38.174 v0.0.1: Updates to RRC re-establishment requirements for IAB MT |
Ericsson |
R4-2007994 |
TP to TS 38.174 v0.0.1: Updates to RRC re-direction requirements for IAB MT |
Ericsson |
R4-2008597 |
TP to TS 38.174 v0.0.1: Updates to RRC re-establishment requirements for IAB MT |
Ericsson |
R4-2008598 |
TP to TS 38.174 v0.0.1: Updates to RRC re-direction requirements for IAB MT |
Ericsson |
6.5.3.3 |
MT timing related requirements [NR_IAB-Core] |
|
R4-2008197 |
discussion on Tansmit Timing requirement for IAB-MT |
Nokia, Nokia Shanghai Bell |
R4-2008198 |
CR on 38174 Transmit Timing requirements for IAB-MT |
Nokia, Nokia Shanghai Bell |
R4-2008239 |
CR on 38174 Transmit Timing requirements for IAB-MT |
Nokia, Nokia Shanghai Bell |
R4-2008599 |
TP to TS 38174 Transmit Timing requirements for IAB-MT |
Nokia |
6.5.3.4 |
RLM requirements [NR_IAB-Core] |
|
R4-2006016 |
on RLM requirements for IAB MT |
ZTE Corporation |
R4-2006017 |
TP for IAB RLM |
ZTE Corporation |
R4-2006433 |
Radio Link Monitoring requirement for IAB-MT |
Samsung |
R4-2007490 |
Discussion regarding RLM requirements of IAB-MTs |
Qualcomm |
R4-2007684 |
Discussion on RLM requirement for IAB-MT |
Huawei, Hisilicon |
R4-2008600 |
TP for IAB RLM |
ZTE Corporation |
6.5.3.5 |
BFR requirements [NR_IAB-Core] |
|
R4-2006015 |
on BFD and BFR requirements for IAB MT |
ZTE Corporation |
R4-2006434 |
Link Recovery requirement for IAB-MT |
Samsung |
R4-2006435 |
TP to TS 38.174 v0.0.1: Beam Candidate Detection Requirements for IAB MT |
Samsung |
R4-2007486 |
TP regarding BFD requirements of IAB-MTs |
Qualcomm |
R4-2007487 |
Discussion regarding BFD and CBD requirements of IAB-MTs |
Qualcomm |
R4-2007683 |
Discussion on BFD and CBD requirement for IAB-MT |
Huawei, Hisilicon |
R4-2008601 |
TP to TS 38.174 v0.0.1: Beam Candidate Detection Requirements for IAB MT |
Samsung |
R4-2008611 |
TP to TS 38.174 on BFD requirements of IAB-MTs |
Qualcomm |
6.5.4 |
EMC core requirements [NR_IAB-Core] |
|
R4-2007054 |
Discussion on IAB EMC requirements |
Ericsson |
R4-2007055 |
TP to TR 38.809 on IAB EMC Emissions |
Ericsson |
R4-2007056 |
TP to TR 38.809 on IAB EMC Immunity |
Ericsson |
R4-2007057 |
TP to TR 38.809 on IAB EMC General |
Ericsson |
R4-2007538 |
[IAB EMC]further discussion on IAB EMC emission requirement |
ZTE Corporation |
R4-2007539 |
[IAB EMC]further discussion on IAB EMC radiated immunity requirement |
ZTE Corporation |
R4-2007540 |
[IAB EMC]on how to handle IAB EMC |
ZTE Corporation |
R4-2007541 |
[IAB EMC]TP to TR IAB EMC emission requirements |
ZTE Corporation |
R4-2007542 |
[IAB EMC]TP to TR IAB EMC immunity requirements |
ZTE Corporation |
R4-2008730 |
TP to TR 38.809 on IAB EMC Emissions |
Ericsson |
R4-2008731 |
[IAB EMC]TP to TR IAB EMC immunity requirements |
ZTE Corporation |
R4-2008732 |
WF on IAB EMC |
ZTE |
6.6.1 |
General [LTE_NR_DC_CA_enh-Core] |
|
R4-2006360 |
Views on P-Max for FR2 |
Apple Inc. |
R4-2006585 |
On p-Max for FR2 |
Nokia, Nokia Shanghai Bell |
R4-2006586 |
Introduction of p-Max to FR2 |
Nokia, Nokia Shanghai Bell |
R4-2006587 |
draft Reply LS on power control for NR-DC |
Nokia, Nokia Shanghai Bell |
R4-2006655 |
Reconsideration of mandatory UL NR-CA and NR-DC |
T-Mobile USA |
R4-2008305 |
Email discussion summary for [95e][115] LTE_NR_DC_CA_enh_RF |
Moderator (Ericsson) |
R4-2008458 |
WF on a P-Max limitation for FR2 in terms of TRP |
Qualcomm |
R4-2008459 |
WF on single UL for DC-12-n71 |
Huawei |
R4-2008945 |
Email discussion summary for [95e][115] LTE_NR_DC_CA_enh_RF |
Moderator (Ericsson) |
6.6.2 |
RF requirements [LTE_NR_DC_CA_enh-Core] |
|
R4-2006451 |
CR for TS 38.101-1: UL harmonic MSD and OOBB exception |
MediaTek Inc. |
R4-2006566 |
Pmax in FR2 |
Intel Corporation |
R4-2006828 |
Views on P-max for FR2 in Rel-16 |
MediaTek Inc. |
R4-2006997 |
CR to TS38.101-1: Introduction of NR DC(Clauses 3 |
ZTE Corporation, Ercisson |
R4-2007048 |
The blind scheme for FDD-TDD EN-DC PC2 adopted for inter-band TDD-TDD EN-DC PC2 |
Ericsson |
R4-2007049 |
Introduction of cell-specific and UE-specific P-Max for FR2 |
Ericsson, Sony |
R4-2007799 |
CR to 38.101-1 for Introduction of requirements for NR-DC |
Ericsson |
R4-2007917 |
Introduction of cell-specific and user-specific P-Max for FR2 |
Ericsson, Sony |
R4-2008053 |
p-max feasibility for Fr2 |
Qualcomm Incorporated |
R4-2008083 |
Discussion on RF requirements about DC_12_n71 |
Huawei, HiSilicon |
R4-2008084 |
CR for 38.101-3 to specify the RF requirements for DC_12_n71 |
Huawei, HiSilicon |
R4-2008265 |
Further discussion on the necessity of p-UE-FR2 |
vivo |
R4-2008266 |
Draft Reply LS on power control for NR-DC |
vivo |
R4-2008272 |
Introduction of P-max in FR2 |
NTT DOCOMO INC. |
R4-2008460 |
The blind scheme for FDD-TDD EN-DC PC2 adopted for inter-band TDD-TDD EN-DC PC2 |
Ericsson |
R4-2009178 |
CR to 38.101-1 for Introduction of requirements for NR-DC |
Ericsson |
6.6.3 |
RRM core requirements (38.133) [LTE_NR_DC_CA_enh-Core] |
|
R4-2008501 |
Email discussion summary for [95e][212] LTE_NR_DC_CA_RRM_1 |
Moderator (Nokia) |
R4-2008502 |
Email discussion summary for [95e][213] LTE_NR_DC_CA_RRM_2 |
Moderator (Ericsson) |
R4-2008602 |
WF on MR-DC EMR RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2008607 |
WF on SCell dormancy |
Ericsson |
R4-2009024 |
Email discussion summary for [95e][212] LTE_NR_DC_CA_RRM_1 |
Moderator (Nokia) |
R4-2009025 |
Email discussion summary for [95e][213] LTE_NR_DC_CA_RRM_2 |
Moderator (Ericsson) |
R4-2009121 |
LS on search threshold for EMR measurements |
RAN4 |
R4-2009263 |
WF on MR-DC EMR RRM requirements |
Nokia, Nokia Shanghai Bell |
6.6.3.1 |
Early Measurement reporting [LTE_NR_DC_CA_enh-Core] |
|
R4-2007281 |
Early measurement reporting in MR-DC |
Qualcomm Incorporated |
R4-2007965 |
On measurement capability for EMR |
Ericsson |
R4-2007966 |
Response LS on clarification of UE requirements for early measurement performance and reporting |
Ericsson |
R4-2009116 |
Response LS on clarification of UE requirements for early measurement performance and reporting |
RAN4 |
6.6.3.1.1 |
NR measurements for EMR [LTE_NR_DC_CA_enh-Core] |
|
R4-2007151 |
NR EMR requirements for 38.133 |
Nokia, Nokia Shanghai Bell |
R4-2007152 |
TP for NR MR-DC RRM requirements for 38.133 |
Nokia, Nokia Shanghai Bell |
R4-2007153 |
Big CR Introduction of UE requirement for MR-DC early measurement reporting in 38.133 |
Nokia, Nokia Shanghai Bell |
R4-2007832 |
Discussion on early measurement in NR |
Huawei, HiSilicon |
R4-2007833 |
CR to introduce EMR in 38.133 |
Huawei, HiSilicon |
R4-2008603 |
Big CR Introduction of UE requirement for MR-DC early measurement reporting in 38.133 |
Nokia, Nokia Shanghai Bell |
R4-2009264 |
Big CR Introduction of UE requirement for MR-DC early measurement reporting in 38.133 |
Nokia, Nokia Shanghai Bell |
6.6.3.1.2 |
LTE NR Inter-RAT EMR [LTE_NR_DC_CA_enh-Core] |
|
R4-2007154 |
NR inter-RAT EMR requirements for 36.133 |
Nokia, Nokia Shanghai Bell |
R4-2007155 |
TP for NR inter-RAT EMR requirements for 36.133 |
Nokia, Nokia Shanghai Bell |
R4-2007156 |
Big CR Introduction of UE requirement for MR-DC early measurement reporting in 36.133 |
Nokia, Nokia Shanghai Bell |
R4-2007834 |
Discussion on LTE |
Huawei, HiSilicon |
R4-2007835 |
CR to introduce EMR in 36.133 |
Huawei, HiSilicon |
R4-2008604 |
CR Introduction of UE requirement for MR-DC early measurement reporting in 36.133 |
Nokia, Nokia Shanghai Bell |
6.6.3.2 |
Efficient and low latency serving cell configuration, activation and setup [LTE_NR_DC_CA_enh-Core] |
|
R4-2007655 |
Further discussion on clarification of UE requirements for early measurement performance and reporting |
ZTE |
R4-2007656 |
Reply LS on clarification of UE requirements for early measurement performance and reporting |
ZTE |
6.6.3.2.1 |
Direct SCell activation [LTE_NR_DC_CA_enh-Core] |
|
R4-2006063 |
[CR] Delay requirements for direct SCell activation |
ZTE Corporation |
R4-2006885 |
Discussion on LTE CRS based and NR SSB based measurement in NR IDLE/INACTIVE mode |
MediaTek inc. |
R4-2007343 |
On NR Measurement for EMR |
OPPO |
R4-2007654 |
Discussion on NR EMR measurements |
ZTE |
R4-2007782 |
CR 38.133 (8.3.4-5) Corrections to Direct SCell activation |
Ericsson |
R4-2007785 |
CR 38.133 (8.3.4-5) Addition of interruption windows for Direct SCell Activation |
Ericsson |
R4-2007836 |
CR on interruption requirements for direct SCell activation for 38.133 |
Huawei, HiSilicon |
R4-2007837 |
CR on interruption requirements for direct SCell activation for 36.133 |
Huawei, HiSilicon |
R4-2008605 |
CR 38.133 (8.3.4-5) Addition of interruption windows for Direct SCell Activation |
Ericsson |
R4-2008606 |
CR on interruption requirements for direct SCell activation for 36.133 |
Huawei, HiSilicon |
6.6.3.2.2 |
SCell dormancy [LTE_NR_DC_CA_enh-Core] |
|
R4-2006520 |
On Scell domancy RRM requirements |
vivo |
R4-2006886 |
Discussion on NR SSB based measurement in LTE IDLE/INACTIVE mode |
MediaTek inc. |
R4-2007157 |
SCell Dormancy requirements discussion |
Nokia, Nokia Shanghai Bell |
R4-2007282 |
Scell BWP dormancy |
Qualcomm Incorporated |
R4-2007288 |
Discussion on RRM requirements for SCell dormancy |
NEC |
R4-2007344 |
On LTE NR inter-RAT EMR |
OPPO |
R4-2007786 |
On SCell dormancy |
Ericsson |
R4-2007838 |
Discussion on SCell dormancy |
Huawei, HiSilicon |
R4-2007839 |
CR on delay requirements for SCell dormancy |
Huawei, HiSilicon |
R4-2007840 |
CR on interruption requirements for SCell dormancy |
Huawei, HiSilicon |
R4-2008187 |
Impact analysis on dormant BWP configuration |
Futurewei Technologies |
R4-2008199 |
Reply LS to RAN2 on dormant BWP |
Futurewei Technologies |
R4-2008608 |
CR on delay requirements for SCell dormancy |
Huawei, HiSilicon |
R4-2008609 |
CR on interruption requirements for SCell dormancy |
Huawei, HiSilicon |
R4-2008610 |
Reply LS to RAN2 on dormant BWP |
Futurewei Technologies |
R4-2009245 |
Reply LS to RAN2 on dormant BWP |
RAN4 |
6.7.2 |
RRM core requirements (38.133) [NR_UE_pow_sav-Core] |
|
R4-2006518 |
CR for maximum MIMO layer adaptation |
vivo,CATT |
R4-2007440 |
CR for maximum MIMO layer adaptation |
vivo,CATT |
R4-2008503 |
Email discussion summary for [95e][214] NR_UE_pow_sav_RRM |
Moderator (CATT) |
R4-2008612 |
WF on RRM measurement relaxation for Power Saving |
CATT |
R4-2009026 |
Email discussion summary for [95e][214] NR_UE_pow_sav_RRM |
Moderator (CATT) |
R4-2009131 |
WF on RRM measurement relaxation for Power Saving |
CATT |
R4-2009265 |
WF on RRM measurement relaxation for Power Saving |
CATT |
6.7.2.1 |
RRM measurement relaxation [NR_UE_pow_sav-Core] |
|
R4-2006198 |
On remaining issues for RRM power saving |
Apple |
R4-2006219 |
Further discussion on the remaining issues for RRM measurement relaxation |
CATT |
R4-2006220 |
CR on measurement relaxation in idle mode for UE power saving |
CATT |
R4-2006221 |
CR on minimum requirement at transition period for UE power saving |
CATT |
R4-2006516 |
On remaining issues on NR UE power savings |
vivo |
R4-2006517 |
LS on RRM relaxation in UE power saving |
vivo |
R4-2006519 |
Draft CR on IDLE state measurement relaxation for UE power saving |
vivo |
R4-2006695 |
Performance Impact on measurement relaxation for power saving |
LG Electronics Inc. |
R4-2006698 |
LS on measurement relaxation for inter-frequency on power saving |
LG Electronics Inc. |
R4-2006810 |
RRM measurement relaxation for UE power saving |
CMCC |
R4-2006884 |
Discussion on RRM measurement relaxation for RRC_IDLE/INACTIVE |
MediaTek inc. |
R4-2006993 |
Draft CR on IDLE state measurement relaxation for UE power saving |
vivo |
R4-2007158 |
RRM requirements for UE Power Saving |
Nokia, Nokia Shanghai Bell |
R4-2007345 |
On RRM measurement relaxation for power saving |
OPPO |
R4-2007495 |
RRM measurement relaxation for power saving |
Qualcomm |
R4-2007728 |
Discussion on measurement relaxation in power saving |
Huawei, Hisilicon |
R4-2007729 |
Discussion on the remaining issues in power saving |
Huawei, Hisilicon |
R4-2007730 |
CR on measurement relaxation for power saving |
Huawei, Hisilicon |
R4-2007892 |
Discussions on RRM impact of NR UE power saving |
Ericsson |
R4-2007893 |
Measurement requirements for UEs under power saving mode |
Ericsson |
R4-2008613 |
LS on RRM relaxation in UE power saving |
vivo |
R4-2008614 |
CR on minimum requirement at transition period for UE power saving |
CATT |
R4-2008615 |
Measurement requirements for UEs under power saving mode |
Ericsson |
R4-2009132 |
LS on RRM relaxation in UE power saving |
RAN4 |
R4-2009133 |
Measurement requirements for UEs under power saving mode |
Ericsson |
R4-2009244 |
CR on minimum requirement at transition period for UE power saving |
CATT |
6.7.3 |
Demodulation and CSI requirements (38.101-4) [NR_UE_pow_sav-Perf |
|
R4-2006199 |
Further discussion on demod test case with MIMO layer adaptation |
Apple |
R4-2006200 |
CR on max MIMO layer assumption in TS38.101-4 |
Apple |
R4-2006245 |
Further discussion on PDCCH-WUS demodulation test for power saving |
CATT |
R4-2006246 |
Applicability of 4Rx demodulation performance for UEs with max MIMO layer adaption |
CATT |
R4-2006811 |
Demodulation on UE power saving |
CMCC |
R4-2006813 |
Discussion on performance requirements for PDCCH-WUS |
MediaTek inc. |
R4-2007229 |
Discussion on the performance requirements for NR power saving |
Huawei, HiSilicon |
R4-2007270 |
Discussion on demod requirement impact of UE power saving |
vivo |
R4-2007381 |
Demodulation requirements for 4Rx UEs with maxMIMO-layers |
Ericsson |
R4-2007494 |
Impact of MIMO layer adaptation on demod requirements |
Qualcomm |
R4-2008705 |
Email discussion summary for [95e][316] NR_UE_pow_sav_Demod |
Moderator (CATT) |
R4-2008802 |
WF on power saving demodulation |
CATT |
R4-2008803 |
Simulation assumption for PDCCH-WUS test |
Media Tek |
R4-2008804 |
CR on max MIMO layer assumption in TS38.101-4 |
Apple |
R4-2008886 |
Email discussion summary for [95e][316] NR_UE_pow_sav_Demod |
Moderator (CATT) |
6.8 |
NR Positioning Support [NR_pos] |
|
R4-2008504 |
Email discussion summary for [95e][215] NR_pos_RRM_1 |
Moderator (Huawei, HiSilicon) |
R4-2008505 |
Email discussion summary for [95e][216] NR_pos_RRM_2 |
Moderator (Intel Corporation) |
R4-2008506 |
Email discussion summary for [95e][217] NR_pos_RRM_3 |
Moderator (Ericsson) |
R4-2008664 |
WF on requirements for RSTD and UE Rx-Tx time difference measurement |
Huawei, HiSilicon |
R4-2008666 |
WF on requirements for NR Positioning PRS-RSRP, SSB and CSI-RS RSRP/RSRQ measurements |
Intel |
R4-2008667 |
WF on impact of NR positioning measurements on RRM |
Ericsson |
R4-2008668 |
WF on gNB requirements for NR positioning |
Ericsson |
R4-2008669 |
LS on UE capability for concurrent processing of PRS and RRM measurements |
Qualcomm |
R4-2009027 |
Email discussion summary for [95e][215] NR_pos_RRM_1 |
Moderator (Huawei, HiSilicon) |
R4-2009028 |
Email discussion summary for [95e][216] NR_pos_RRM_2 |
Moderator (Intel Corporation) |
R4-2009029 |
Email discussion summary for [95e][217] NR_pos_RRM_3 |
Moderator (Ericsson) |
R4-2009111 |
LS on intra/inter-frequency measurement for NR positioning |
RAN4 |
R4-2009139 |
WF on requirements for NR Positioning PRS-RSRP, SSB and CSI-RS RSRP/RSRQ measurements |
Intel |
R4-2009261 |
WF on impact of NR positioning measurements on RRM |
Ericsson |
R4-2009266 |
WF on impact of NR positioning measurements on RRM |
Ericsson |
6.8.1 |
General [NR_pos-Core/Perf] |
|
R4-2006560 |
CR to TS 38.133: Structure for NR positioning RRM requirements |
Intel Corporation |
R4-2006561 |
CR to TS 38.133: PRS RSTD requirements |
Intel Corporation |
R4-2006562 |
Views on down scoping for NR positioning remaining issues |
Intel Corporation |
R4-2007271 |
Discussion on the SRS for positioning during the DRX inactive period |
vivo |
6.8.2.1 |
UE requirements [NR_pos-Core] |
|
R4-2007952 |
On new measurement gaps for NR positioning |
Ericsson |
R4-2007953 |
LS on measurement gaps for NR positioning |
Ericsson |
R4-2007955 |
Positioning measurement accuracy requirements structure in section 10 |
Ericsson |
R4-2009120 |
LS on measurement gaps for NR positioning |
Ericsson |
R4-2009126 |
Positioning measurement accuracy requirements structure in section 10 |
Ericsson |
R4-2009246 |
LS on measurement gaps for NR positioning |
RAN4 |
6.8.2.1.1 |
PRS-RSTD measurements [NR_pos-Core] |
|
R4-2006018 |
PRS-RSTD measurements for NR positioning |
ZTE Corporation |
R4-2006168 |
On PRS-RSTD measurements for NR positioning |
Qualcomm Incorporated |
R4-2006232 |
Discussion on RSTD measurement requirements |
CATT |
R4-2006304 |
Discussion of remaining issues for PRS-RSTD measurement |
MediaTek inc. |
R4-2006556 |
Further discussion on NR PRS RSTD requirements |
Intel Corporation |
R4-2007145 |
Scaling of measurement period due to UE Rx beam sweeping |
ZTE Corporation |
R4-2007841 |
Discussion on RSTD measurement |
Huawei, HiSilicon |
R4-2007842 |
[draft] reply LS on agreements related to NR Positioning |
Huawei, HiSilicon |
R4-2007944 |
On PRS RSTD measurements |
Ericsson |
R4-2007945 |
On PRS RSTD measurement report mapping |
Ericsson |
R4-2007946 |
Measurement report mapping for PRS RSTD |
Ericsson |
R4-2007949 |
On additional path reporting with positioning measurements |
Ericsson |
R4-2007950 |
Additional path report mapping for RSTD |
Ericsson |
R4-2007958 |
Reporting criteria for NR RSTD |
Ericsson |
R4-2009112 |
Measurement report mapping for PRS RSTD |
Ericsson |
R4-2009114 |
Reporting criteria for NR RSTD |
Ericsson |
R4-2009253 |
Measurement report mapping for PRS RSTD |
Ericsson |
R4-2009257 |
Reporting criteria for NR RSTD |
Ericsson |
6.8.2.1.2 |
PRS-RSRP measurements [NR_pos-Core] |
|
R4-2006169 |
On PRS-RSRP measurements for NR positioning |
Qualcomm Incorporated |
R4-2006233 |
Discussion on PRS-RSRP measurement requirements |
CATT |
R4-2006238 |
CR on PRS-RSRP measurement report mapping |
CATT |
R4-2006305 |
Discussion of remaining issues for PRS-RSRP measurement |
MediaTek inc. |
R4-2007843 |
Discussion on PRS-RSRP measurement |
Huawei, HiSilicon |
R4-2007844 |
CR for measurement requriements for PRS-RSRP |
Huawei, HiSilicon |
R4-2007947 |
On PRS-RSRP measurements |
Ericsson |
R4-2007948 |
On PRS-RSRP measurement report mapping |
Ericsson |
R4-2007951 |
Additional path report mapping for UE Rx-Tx |
Ericsson |
R4-2007960 |
Reporting criteria for PRS-RSRP |
Ericsson |
R4-2008665 |
CR on PRS-RSRP measurement report mapping |
CATT |
R4-2009129 |
CR on PRS-RSRP measurement report mapping |
CATT |
6.8.2.1.3 |
Rx-Tx time difference measurements [NR_pos-Core] |
|
R4-2006170 |
On UE Rx-Tx time difference measurement for NR positioning |
Qualcomm Incorporated |
R4-2006234 |
Discussion on UE Rx-Tx time difference measurement requirements |
CATT |
R4-2006237 |
Link level simulation assumption for UE RX-Tx time difference |
CATT |
R4-2006557 |
Further discussion on UE Rx-Tx time difference requirements |
Intel Corporation |
R4-2007845 |
Discussion on Rx-Tx time difference measurement |
Huawei, HiSilicon |
R4-2007943 |
On UE Rx-Tx measurements |
Ericsson |
R4-2007954 |
Link-level simulation assumptions for UE Rx-Tx |
Ericsson |
R4-2007956 |
On criterion of pathloss measurement failure for power control of SRS for positioning |
Ericsson |
R4-2007957 |
Response LS on criterion of pathloss measurement failure for power control of SRS for positioning |
Ericsson |
R4-2007959 |
Reporting criteria for NR UE Rx-Tx |
Ericsson |
R4-2007995 |
Impact of NTA offset on UE Rx-Tx time difference measurement |
Ericsson |
R4-2007996 |
LS on impact of NTA offset on UE Rx-Tx time difference measurement |
Ericsson |
R4-2007997 |
Analysis of UE Rx-Tx Measurement Report Mapping in NR |
Ericsson |
R4-2007998 |
UE Rx-Tx Measurement Report Mapping in NR in 38.133 |
Ericsson |
R4-2008673 |
Response LS on criterion of pathloss measurement failure for power control of SRS for positioning |
Ericsson |
R4-2009113 |
UE Rx-Tx Measurement Report Mapping in NR in 38.133 |
Ericsson |
R4-2009119 |
LS on impact of NTA offset on UE Rx-Tx time difference measurement |
Ericsson |
R4-2009247 |
Response LS on criterion of pathloss measurement failure for power control of SRS for positioning |
RAN4 |
R4-2009254 |
UE Rx-Tx Measurement Report Mapping in NR in 38.133 |
Ericsson |
R4-2009267 |
LS on impact of NTA offset on UE Rx-Tx time difference measurement |
RAN4 |
6.8.2.1.4 |
SSB and CSI-RS RSRP/RSRQ measurements [NR_pos-Core] |
|
R4-2007939 |
NR E-CID reporting criteria requirements |
Ericsson |
R4-2007940 |
NR E-CID measurement requirements |
Ericsson |
R4-2009103 |
NR E-CID reporting criteria requirements |
Ericsson |
R4-2009104 |
NR E-CID measurement requirements |
Ericsson |
6.8.2.1.5 |
Link-level evaluations for PRS-RSTD and PRS-RSRP [NR_pos-Core] |
|
R4-2006171 |
Link-level simulation assumptions for UE Rx-Tx time difference measurements |
Qualcomm Incorporated |
R4-2006559 |
Link-level simulation assumptions for UE Rx-Tx time difference measurement |
Intel Corporation |
R4-2007941 |
Updated link simulation results for NR RSTD |
Ericsson |
R4-2007942 |
Updated link simulation results for PRS RSRP |
Ericsson |
R4-2009127 |
Link-level simulation assumptions for UE Rx-Tx time difference measurements |
Qualcomm Incorporated |
6.8.2.2 |
Impact on existing RRM requirements [NR_pos-Core] |
|
R4-2006173 |
On Impact of NR positioning on existing RRM requirements |
Qualcomm Incorporated |
R4-2006236 |
Impact on existing RRM measurement |
CATT |
R4-2006306 |
Discussion on impact on existing RRM requirements |
MediaTek inc. |
R4-2006555 |
Further discussion on UE RRM impacts due to NR Pos measurement |
Intel Corporation |
R4-2007144 |
BWP switch during gaps used for PRS measurements |
ZTE Corporation |
R4-2007846 |
Impact of positioning on existing RRM requirements |
Huawei, HiSilicon |
R4-2007999 |
Impact of active BWP change on positioning measurements |
Ericsson |
6.8.2.3 |
gNB requirements [NR_pos-Core] |
|
R4-2006024 |
gNB requirements for NR positioning |
ZTE Corporation |
R4-2006172 |
on gNB requirements for NR positioning |
Qualcomm Incorporated |
R4-2006235 |
Discussion on gNB measurement requirements |
CATT |
R4-2006239 |
CR on UL RTOA measurement report mapping |
CATT |
R4-2006240 |
CR on gNB Rx-Tx time difference measurement report mapping |
CATT |
R4-2006241 |
CR on SRS RSRP measurement report mapping |
CATT |
R4-2006558 |
Further discussion on gNB measurement requirements in NR Positioning |
Intel Corporation |
R4-2007116 |
On gNB measurement accuracy requirements for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2007275 |
Optionality for positioning measurements in gNB |
Ericsson |
R4-2007277 |
Side conditions for gNB measurement accuracy |
Ericsson |
R4-2007278 |
Beam configuration for gNB measurement accuracy |
Ericsson |
R4-2007286 |
PRS/SRS configurations for gNB measurement accuracy |
Ericsson |
R4-2007304 |
Applicability of gNB Rx-Tx accuracy under TA change |
Ericsson |
R4-2007305 |
Accuracy for different BS types |
Ericsson |
R4-2007336 |
gNB Positioning Measurement Report Mapping |
Ericsson |
R4-2007847 |
Discussion on the scope gNB requirements for NR positioning |
Huawei, HiSilicon, CMCC |
R4-2007848 |
Discussion on gNB positioning measurement requirements |
Huawei, HiSilicon |
R4-2007849 |
CR for gNB Rx-Tx time difference and UL-RTOA report mapping |
Huawei, HiSilicon |
R4-2007850 |
CR for SRS-RSRP report mapping |
Huawei, HiSilicon |
R4-2007851 |
CR for AoA/ZoA report mapping |
Huawei, HiSilicon |
R4-2008670 |
CR on SRS RSRP measurement report mapping |
CATT |
R4-2008671 |
CR for gNB Rx-Tx time difference and UL-RTOA report mapping |
Huawei, HiSilicon |
R4-2008672 |
CR for AoA/ZoA report mapping |
Huawei, HiSilicon |
6.8.2.4 |
Others [NR_pos-Core] |
|
R4-2007117 |
On UE aspects for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2007852 |
Discussion on criterion for inaccurate pathloss measurement |
Huawei, HiSilicon |
R4-2007853 |
[draft] reply LS on criterion of pathloss measurement failure for power control of SRS for positioning |
Huawei, HiSilicon |
R4-2007854 |
Discussion on positioning SRS during DRX inactive time |
Huawei, HiSilicon |
R4-2007855 |
[draft] reply LS on positioning SRS during DRX inactive time |
Huawei, HiSilicon |
R4-2008674 |
Reply LS on positioning SRS during DRX inactive time |
Huawei, HiSilicon |
R4-2009248 |
Reply LS on positioning SRS during DRX inactive time |
Huawei, HiSilicon |
6.9.1 |
Demodulation and CSI requirements [NR_L1enh_URLLC-Perf] |
|
R4-2007593 |
Discussion on URLLC UE requirements applicability |
Intel Corporation |
R4-2008706 |
Email discussion summary for [95e][317] NR_L1enh_URLLC_Demod_Part1 |
Moderator (Ericsson) |
R4-2008707 |
Email discussion summary for [95e][318] NR_L1enh_URLLC_Demod_Part2 |
Moderator (Huawei) |
R4-2008805 |
WF on ultra-low BLER requirements |
Ericsson |
R4-2008806 |
Simulation results summary for ULRRC Ultra-Low BLER test |
Ericsson |
R4-2008807 |
Way forward on NR URLLC UE performance requirements |
Intel |
R4-2008808 |
Simulation assumptions for NR URLLC UE performance requirements test cases |
Intel |
R4-2008809 |
Summary of simulation results for NR URLLC UE FR1 performance requirements |
Huawei, HiSilicon |
R4-2008810 |
Way forward on NR URLLC BS performance requirements |
Huawei, HiSilicon |
R4-2008811 |
Simulation assumptions for NR URLLC BS performance requirements test cases |
Huawei, HiSilicon |
R4-2008812 |
Summary of simulation results for NR URLLC BS FR1 performance requirements |
Huawei, HiSilicon |
R4-2008887 |
Email discussion summary for [95e][317] NR_L1enh_URLLC_Demod_Part1 |
Moderator (Ericsson) |
R4-2008888 |
Email discussion summary for [95e][318] NR_L1enh_URLLC_Demod_Part2 |
Moderator (Huawei) |
6.9.1.1 |
Performance requirements with ultra-low BLER [NR_L1enh_URLLC-Perf] |
|
R4-2006526 |
Discussion on URLLC requirements for Ultra-low BLER |
Intel Corporation |
6.9.1.1.1 |
UE demodulation and CSI requirements (38.101-4) [NR_L1enh_URLLC-Perf] |
|
R4-2006207 |
On UE demodulation and CSI requirements with Ultra-low BLER |
Apple |
R4-2006656 |
Views on URLLC Ultra-low BLER Test Cases |
Qualcomm Incorporated |
R4-2007190 |
Discussion and simulation on URLLC UE high reliability with ultra-low BLER |
Huawei, HiSilicon |
R4-2007933 |
Discussion on UE URLLC performance requirements for Ultra low BLER |
Ericsson |
6.9.1.1.2 |
BS demodulation requirements (38.104) [NR_L1enh_URLLC-Perf] |
|
R4-2006060 |
On NR Rel-16 high reliability BS demodulation test feasibility and requirements |
Nokia, Nokia Shanghai Bell |
R4-2006061 |
NR Rel-16 non-relaxed high reliability BS demodulation requirement simulation results |
Nokia, Nokia Shanghai Bell |
R4-2006325 |
Discussion and initial simulation results for URLLC ultra-low BLER requirement |
Samsung |
R4-2007187 |
Views on NR BS performance for ultra-low BLER |
NTT DOCOMO, INC. |
R4-2007191 |
Discussion and simulation on URLLC BS high reliability with ultra-low BLER |
Huawei, HiSilicon |
R4-2007364 |
URLLC BS ultra-low BLER test |
Ericsson |
6.9.1.2.1 |
UE demodulation and CSI requirements (38.101-4) [NR_L1enh_URLLC-Perf] |
|
R4-2006208 |
On UE demodulation and CSI requirements with higher BLER |
Apple |
R4-2006527 |
Discussion on UE performance requirements for URLLC |
Intel Corporation |
R4-2007141 |
Views on UE demodulation for URLLC requirements |
NTT DOCOMO, INC. |
R4-2007192 |
Discussion and simulation on URLLC UE PDSCH demodulation requirements for high reliability with higher BLER |
Huawei, HiSilicon |
R4-2007193 |
Discussion and simulation on URLLC UE performance requirements for PDSCH mapping Type B and processing capabiltiy 2 |
Huawei, HiSilicon |
R4-2007194 |
Discussion on URLLC UE performance requirements for low latency for pre-emption |
Huawei, HiSilicon |
R4-2007195 |
Discussion on URLLC UE CQI reporting requirements |
Huawei, HiSilicon |
R4-2007801 |
Views on URLLC High BLER Test Cases |
Qualcomm Incorporated |
R4-2007929 |
Discussion on UE performance requirements for Pre-emption |
Ericsson |
R4-2007930 |
Discussion on UE URLLC performance requirements for Slot Aggregation |
Ericsson |
R4-2007931 |
URLLC UE test applicability and specification layout |
Ericsson |
R4-2007932 |
Views on UE URLLC performance requirements for Type B and PDSCH capability 2 |
Ericsson |
6.9.1.2.2 |
BS demodulation requirements (38.104) [NR_L1enh_URLLC-Perf] |
|
R4-2006062 |
On NR Rel-16 relaxed high reliability and low latency BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2006326 |
View on remain issues for URLLC performance requirements in NR Rel-16 |
Samsung |
R4-2006528 |
Discussion on BS performance requirements for URLLC |
Intel Corporation |
R4-2006582 |
NR Rel-16 relaxed high reliability and low latency BS demodulation requirement simulation results |
Nokia, Nokia Shanghai Bell |
R4-2007188 |
Views on NR BS performance for high-reliability and low-latency |
NTT DOCOMO, INC. |
R4-2007196 |
Discussion and simulation on URLLC BS PUSCH demodulation requirements for high reliability with higher BLER |
Huawei, HiSilicon |
R4-2007197 |
Discussion and simulation on URLLC BS performance requirements for low latency |
Huawei, HiSilicon |
R4-2007362 |
URLLC in BS specifications |
Ericsson |
R4-2007363 |
URLLC BS demod rquirements |
Ericsson |
6.10 |
Single radio voice call continuity from 5G to 3G (SRVCC) [SRVCC_NR_to_UMTS-Core] |
|
R4-2008507 |
Email discussion summary for [95e][218] SRVCC_NR_to_UMTS_RRM |
Moderator (Huawei, HiSilicon) |
R4-2009030 |
Email discussion summary for [95e][218] SRVCC_NR_to_UMTS_RRM |
Moderator (Huawei, HiSilicon) |
6.10.1 |
RRM core requirements maintenance (38.133) [SRVCC_NR_to_UMTS-Core] |
|
R4-2006987 |
Gap applicability errors corrected for SRVCC |
Ericsson |
6.10.2 |
RRM perf requirements (38.133) [SRVCC_NR_to_UMTS-Perf] |
|
R4-2006986 |
SRVCC test case for event triggered reporting |
Ericsson |
R4-2007755 |
Test case for NR to UTRA FDD Inter-RAT handover |
Huawei, Hisilicon |
R4-2008616 |
SRVCC test case for event triggered reporting |
Ericsson |
R4-2008617 |
Test case for NR to UTRA FDD Inter-RAT handover |
Huawei, Hisilicon |
R4-2009136 |
SRVCC test case for event triggered reporting |
Ericsson |
6.11.1 |
UE RF core requirements (38.101) [NR_eMIMO-Core] |
|
R4-2008306 |
Email discussion summary for [95e][116] NR_eMIMO_UE_RF |
Moderator (Samsung) |
R4-2008461 |
WF on MPR with Pi/2 BPSK DMRS |
Qualcomm |
R4-2008462 |
WF on Uplink Full Power Transmission |
Samsung |
R4-2008465 |
WF on Enabling Transparent TxD in Rel-16 |
Qualcomm |
R4-2008946 |
Email discussion summary for [95e][116] NR_eMIMO_UE_RF |
Moderator (Samsung) |
R4-2009171 |
LS on clarification of transparent diversity feasibility |
RAN4 |
6.11.1.1 |
DMRS enhancement with PI/2 BPSK [NR_eMIMO-Core] |
|
R4-2006494 |
MPR With PI/2 BPSK DMRS |
Nokia |
R4-2006822 |
Pi_2 BPSK DMRS Investigation |
Qualcomm Incorporated |
R4-2008216 |
On Pi/2 BPSK DMRS |
Huawei, HiSilicon |
6.11.1.2 |
Uplink Tx Full Power transmission [NR_eMIMO-Core] |
|
R4-2006345 |
On UL Full Power Transmission |
Apple Inc. |
R4-2006367 |
Discussion on Uplink Full Power Transmission (ULFPTx) |
Samsung |
R4-2006368 |
CR to TS38.101-1 on introduction of Uplink Full Power Transmission |
Samsung |
R4-2006369 |
CR to TS38.101-2 on introduction of Uplink Full Power Transmission |
Samsung |
R4-2006668 |
[NR_eMIMO] RIMD impact on EVM and MPR for UL MIMO and Tx Diversity |
Skyworks Solutions Inc. |
R4-2006779 |
CR to clarify UE SRS port configuration for UL tests |
Qualcomm Incorporated |
R4-2007050 |
Verification of FP modes and relation to Rel-15 requirements |
Ericsson |
R4-2007051 |
Specification framework for introduction of requirements for the FP modes |
Ericsson |
R4-2007078 |
Further on EN-DC and SA power class (Rel-16) |
OPPO |
R4-2007079 |
CR to TS 38.101-3 EN-DC requirement alignment (R16) |
OPPO |
R4-2008048 |
eMIMO FPTX Open items for FR1 |
Qualcomm Incorporated |
R4-2008049 |
Tx diversity open items for Rel-16 |
Qualcomm Incorporated |
R4-2008050 |
draft CR to enable FPULTX |
Qualcomm Incorporated |
R4-2008185 |
On Release 15 and 16 two Intra-band Transmit Chain Cases |
Skyworks Solutions Inc. |
R4-2008217 |
On NR eMIMO full power transmission |
Huawei, HiSilicon |
R4-2008218 |
draft CR for TS 38.101-1 eMIMO full power transmission |
Huawei, HiSilicon |
R4-2008463 |
CR to TS38.101-1 on introduction of Uplink Full Power Transmission |
Samsung |
R4-2008464 |
CR to clarify UE SRS port configuration for UL tests |
Qualcomm Incorporated |
6.11.2 |
RRM core requirements (38.133) [NR_eMIMO-Core] |
|
R4-2008508 |
Email discussion summary for [95e][219] NR_eMIMO_RRM |
Moderator (Samsung) |
R4-2008618 |
WF on NR eMIMO RRM requirements |
Samsung |
R4-2009031 |
Email discussion summary for [95e][219] NR_eMIMO_RRM |
Moderator (Samsung) |
6.11.2.1 |
L1-SINR [NR_eMIMO-Core] |
|
R4-2006205 |
Discussion on requirements for L1-SINR measurements |
Apple |
R4-2006370 |
Discussion on L1-SINR Measurement Requirement |
Samsung |
R4-2006371 |
CR to TS38.133 on introduction of L1-SINR Measurement Requirement (Section 3.3 and 9) |
Samsung |
R4-2006864 |
Discussion on RRM requirements for L1-SINR |
MediaTek inc. |
R4-2007483 |
RRM requirements for L1-SINR estimation |
Qualcomm |
R4-2007767 |
Discussion on L1-SINR measurement requirements for NR eMIMO |
Huawei, HiSilicon |
R4-2007768 |
Discussion on L1-SINR measurement accuracy for NR eMIMO |
Huawei, HiSilicon |
R4-2007769 |
DraftCR on L1-SINR measurement accuracy requirements |
Huawei, HiSilicon |
R4-2008091 |
Discussions on Rel-16 NR eMIMO L1-SINR measurements |
Nokia, Nokia Shanghai Bell |
R4-2008619 |
CR to TS38.133 on introduction of L1-SINR Measurement Requirement (Section 3.3 and 9) |
Samsung |
R4-2009274 |
CR to TS38.133 on introduction of L1-SINR Measurement Requirement (Section 3.3 and 9) |
Samsung |
6.11.2.2 |
SCell Beam failure recovery [NR_eMIMO-Core] |
|
R4-2006372 |
Discussion on SCell Beam Failure Recovery RRM Requirement |
Samsung |
R4-2006373 |
CR to TS38.133 on introduction of SCell BFD and CBD (Section 8.5) |
Samsung |
R4-2006374 |
CR to TS38.133 on introduction of SCell BFRQ Procedure (Section 8.5) |
Samsung |
R4-2006865 |
Discussion on RRM requirements for BFR on SCell |
MediaTek inc. |
R4-2007378 |
BFRQ on SR-like PUCCH resource |
Ericsson |
R4-2007379 |
Draft CR: Correction of SCell BFRQ Procedure (Section 8.5) |
Ericsson |
R4-2007484 |
SCell Beam Failure Detection and Recovery |
Qualcomm |
R4-2007770 |
Discussion on SCell BFD and CBD requiremetns for NR eMIMO |
Huawei, HiSilicon |
R4-2007771 |
CR on SCell BFD and CBD requirements |
Huawei, HiSilicon |
R4-2008620 |
CR on SCell BFD and CBD requirements |
Huawei, HiSilicon |
R4-2008621 |
CR to TS38.133 on introduction of SCell BFRQ Procedure (Section 8.5) |
Samsung |
6.11.2.3 |
DL/UL beam indication with reduced latency and overhead [NR_eMIMO-Core] |
|
R4-2006375 |
Discussion on MAC-CE based spatial relation update for aperiodic SRS |
Samsung |
6.11.2.4 |
Others [NR_eMIMO-Core] |
|
R4-2006065 |
Discussion on applicable timing for the unknown PL RS activated by MAC-CE |
ZTE Corporation |
R4-2006206 |
Discussion on RRM requirements for Multi-TRP |
Apple |
R4-2006376 |
Discussion on MRTD/MTTD requirement to Enable Multi-TRP Transmission |
Samsung |
R4-2006377 |
CR to TS38.133 on introduction of multi-TRP transmission (Section 7.5 and 7.6) |
Samsung |
R4-2006866 |
Discussion on MRTD for multiple TRPs scenario |
MediaTek inc. |
R4-2006867 |
Discussion on PL RS activation requirement via MAC CE |
MediaTek inc. |
R4-2006868 |
CR for introduction of pathloss reference signal switching delay |
MediaTek inc. |
R4-2007380 |
MRTD/MTTD requirements for Multi-TRP deployment for MIMO+CA and MIMO+DC |
Ericsson |
R4-2007485 |
MRTD/MTTD in CA/DC with multiple TRPs |
Qualcomm |
R4-2007772 |
Discussion on MRTD and MTTD requirements for multi-TRP transmissions |
Huawei, HiSilicon |
R4-2008092 |
Discussions on Rel-16 NR eMIMO multi-TRP transmissions |
Nokia, Nokia Shanghai Bell |
R4-2008622 |
CR to TS38.133 on introduction of multi-TRP transmission (Section 7.5 and 7.6) |
Samsung |
6.11.3 |
Demodulation and CSI requirements (38.101-4) [NR_eMIMO-Perf] |
|
R4-2008708 |
Email discussion summary for [95e][319] NR_eMIMO_Demod |
Moderator (Samsung) |
R4-2008813 |
WF for general and PDSCH requirements with Single-DCI SDM scheme and Multi-DCI transmission schemes (eMBB) |
Huawei |
R4-2008814 |
WF for PDSCH requirements with Single-DCI based multi-TRP/Panel transmission schemes (URLLC) |
Intel |
R4-2008815 |
Simulation assumption for PDSCH requirements with Single-DCI SDM scheme and Multi-DCI transmission schemes |
Ericsson |
R4-2008816 |
WF for PMI test case with Rel-16 Type II codebook |
Qualcomm |
R4-2008889 |
Email discussion summary for [95e][319] NR_eMIMO_Demod |
Moderator (Samsung) |
6.11.3.1 |
General [NR_eMIMO-Perf] |
|
R4-2006627 |
Views on test cases for eMIMO |
Qualcomm Incorporated |
6.11.3.2 |
Demodulation requirements [NR_eMIMO-Perf] |
|
R4-2006314 |
Test case design for PDSCH requirements with Multi-TRP/Pannel transmission |
Samsung |
R4-2006316 |
Simulation results for Multi-TRP/Pannel tranmission |
Samsung |
R4-2006539 |
Views on UE demodulation requirements for NR eMIMO |
Intel Corporation |
R4-2006814 |
Discussion on PDSCH performance requirements for Rel-16 eMIMO |
MediaTek inc. |
R4-2007198 |
Discussion on Multi-DCI based PDSCH performance requirements for Multi-TRP in eMIMO |
Huawei, HiSilicon |
R4-2007199 |
Discussion on test scopes and general test setup for PDSCH requirements of NR eMIMO |
Huawei, HiSilicon |
R4-2007385 |
PDSCH requirements with multi-DCI based multi-TRP/Panel transmission |
Ericsson |
R4-2007386 |
PDSCH requirements with single-DCI based multi-TRP/Panel transmission |
Ericsson |
6.11.3.3 |
CSI requirements [NR_eMIMO-Perf] |
|
R4-2006315 |
Test case design for PMI test case with Rel-16 Type II codebook |
Samsung |
R4-2006317 |
Simulation results for PMI test cases with Rel-16 Type II codebook |
Samsung |
R4-2007200 |
Discussion on PMI reporting test for eMIMO |
Huawei, HiSilicon |
R4-2007936 |
Evaluation on test setup for Rel-16 Type II codebook |
Ericsson |
R4-2007937 |
Simulation results for Rel-16 Type II codebook |
Ericsson |
6.12.1 |
General [NR_DL256QAM_FR2] |
|
R4-2006927 |
Draft TR 38.883 for FR2 DL 256QAM v1.3.0 |
China Telecom |
R4-2006928 |
TP for TR 38.883 Editoral corrections |
China Telecom |
R4-2008307 |
Email discussion summary for [95e][117] NR_DL256QAM_FR2 |
Moderator (China Telecom) |
R4-2008947 |
Email discussion summary for [95e][117] NR_DL256QAM_FR2 |
Moderator (China Telecom) |
R4-2008968 |
Draft TR 38.883 for FR2 DL 256QAM v1.4.0 |
China Telecom |
6.12.2 |
BS RF core requirements (38.104) [NR_DL256QAM_FR2] |
|
R4-2007128 |
CR to TS 38.104: Introduction of FR2 DL 256QAM |
Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile, Ericsson |
R4-2007129 |
CR to TS 38.141-2: Introduction of FR2 DL 256QAM |
Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
6.12.3 |
UE RF core requirements (38.101-2) [NR_DL256QAM_FR2] |
|
R4-2007088 |
Maximum Input Level for 256 QAM FR2 |
OPPO |
R4-2007127 |
CR to TS 38.101-2: Introduction of FR2 DL 256QAM |
Nokia, Nokia Shanghai Bell, China Telecom, Verizon, NTT Docomo, T-Mobile |
6.12.4 |
Demodulation and CSI requirements (38.101-4) [NR_DL256QAM_FR2-Perf] |
|
R4-2006041 |
UE demodulation and CSI reporting requirements for FR2 DL 256QAM |
China Telecom |
R4-2006529 |
Discussion on UE performance requirements for FR2 DL 256QAM |
Intel Corporation |
R4-2007138 |
Views on DL 256QAM requirements for FR2 |
NTT DOCOMO, INC. |
R4-2007230 |
Discussion on the performance requirements for NR DL 256QAM for FR2 |
Huawei, HiSilicon |
R4-2007920 |
TP to TR 38.883: Section 7 Demod test challenges |
Ericsson |
R4-2008709 |
Email discussion summary for [95e][320] NR_DL256QAM_FR2_Demod |
Moderator (China Telecomm) |
R4-2008817 |
WF on UE demodulation and CSI reporting requirements for FR2 DL 256QAM |
China Telecomm |
R4-2008818 |
TP to TR 38.883: Section 7 Demod test challenges |
Ericsson |
R4-2009040 |
Email discussion summary for [95e][320] NR_DL256QAM_FR2_Demod |
Moderator (China Telecomm) |
6.13.1 |
RF core requirements [NR_RF_FR1] |
|
R4-2008308 |
Email discussion summary for [95e][118] NR_RF_FR1_Part_1 |
Moderator (Huawei) |
R4-2008466 |
WF on intra-band contiguous CA MPR and AMPR remaining issues |
Skyworks, Nokia |
R4-2008467 |
WF on DC location of intra-band CA |
Huawei, HiSilicon |
R4-2008469 |
WF on ACS Jammer bandwidth of Bandwidth class C |
Qualcomm |
R4-2008470 |
WF on intra-band UL NC CA UE capability |
Huawei, HiSilicon |
R4-2008471 |
WF on remaining issue on MPR and AMPR for intra-band non-contiguous CA |
Skyworks, Qualcomm |
R4-2008473 |
WF on ULSUP time mask requirement |
Huawei, HiSilicon |
R4-2008948 |
Email discussion summary for [95e][118] NR_RF_FR1_Part_1 |
Moderator (Huawei) |
6.13.1.2 |
Intra-band contiguous DL CA for FR1 [NR_RF_FR1] |
|
R4-2008072 |
CR for 38.101-1 to introduce BCS2 for CA_n78(2A). |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2008146 |
FR1 Intra-band DLCA ACS IBB and Wideband Intermodulation |
Qualcomm Incorporated |
R4-2008147 |
FR1 Intra-band CA ACS IBB and WB IMD |
Qualcomm Incorporated |
R4-2008156 |
CR for 38.101-1 DL RF requirement correction |
Huawei, HiSilicon |
6.13.1.3 |
Intra-band contiguous UL CA for FR1 power class 3 [NR_RF_FR1] |
|
R4-2006637 |
[NR FR1 ULCA] Contiguous Intra-band ULCA Allocation Definitions |
Skyworks Solutions Inc. |
R4-2006638 |
[NR FR1 ULCA] Class B and C UL CA MPR Proposals and A-MPR Evaluation |
Skyworks Solutions Inc. |
R4-2008010 |
ACLR measurement center frequency for NR FR1 contiguous CA |
Nokia, Nokia Shanghai Bell |
R4-2008148 |
on FR1 UL CA MPR requirement Rel-16 |
Huawei, HiSilicon |
R4-2008149 |
on FR1 UL CA DC location |
Huawei, HiSilicon |
R4-2008153 |
CR on FR1 UL contiguous CA requirement |
Huawei, HiSilicon |
R4-2008202 |
Intra-band Contiguous ULCA MBW and ACLR Offset |
Qualcomm Incorporated |
R4-2008207 |
Intra-band Contiguous ULCA MPR |
Qualcomm Incorporated |
R4-2008255 |
[NR FR1 ULCA] Class B and C Bandwidth Verification |
Skyworks Solutions Inc. |
R4-2008468 |
CR on FR1 UL contiguous CA requirement |
Huawei, HiSilicon |
6.13.1.4 |
Intra-band non-contiguous UL CA for FR1 power class 3 [NR_RF_FR1] |
|
R4-2008039 |
[FR1 NR ULCA] Non-contiguous UL CA Architecture, Signaling and MPR evaluation |
Skyworks Solutions Inc. |
R4-2008150 |
on FR1 UL non-contiguous CA UE capability |
Huawei, HiSilicon |
R4-2008151 |
on FR1 UL non-contiguous CA MPR requirement Rel-16 |
Huawei, HiSilicon |
R4-2008165 |
CR for intra-band UL non-contiguous CA requirement |
Huawei, HiSilicon |
R4-2008208 |
Non-contiguous ULCA MPR and Requirements |
Qualcomm Incorporated |
R4-2008472 |
CR for intra-band UL non-contiguous CA requirement |
Huawei, HiSilicon |
6.13.1.5 |
Switching period between case 1 and case 2 [NR_RF_FR1] |
|
R4-2006032 |
Remaining issues for Tx switching between two uplink carriers |
China Telecom |
R4-2006033 |
CR to TS 38.101-1: Switching time mask between two uplink carriers in UL CA and SUL |
China Telecom, ZTE, CMCC, China Unicom, KDDI |
R4-2006034 |
CR to TS 38.101-3: Switching time mask between two uplink carriers in EN-DC |
China Telecom, ZTE, CMCC, China Unicom, KDDI |
R4-2006290 |
Requirements for suppporting Tx switching between two uplink carriers in UL CA and SUL |
CATT |
R4-2006291 |
Requirements for suppporting Tx switching between two uplink carriers in EN-DC |
CATT |
R4-2006364 |
Views on Tx diversity and Tx carrier switching |
Apple Inc. |
R4-2006513 |
Switching between case 1 and case 2 for two NR FR1 carriers |
Nokia, Nokia Shanghai Bell |
R4-2006514 |
CR to TS 38.101-1: Time mask requirements for switching between 1Tx and 2Tx transmissions for inter-band UL CA and SUL case |
Nokia, Nokia Shanghai Bell |
R4-2006515 |
CR to TS 38.101-3: Time mask requirements for switching between 1Tx and 2Tx transmissions for inter-band EN-DC without SUL |
Nokia, Nokia Shanghai Bell |
R4-2006804 |
Requirements for switching between case1 and case2 |
CMCC |
R4-2006943 |
Resolving remaining issues for UE switching between 1Tx carrier and 2Tx carrier |
Huawei, HiSilicon |
R4-2006944 |
Clarification on 2Tx carrier for UE switching between 1Tx carrier and 2Tx carrier |
Huawei, HiSilicon |
R4-2006945 |
CR to 38101-1 on switching between 1Tx carrier and 2Tx carrier |
Huawei, HiSilicon |
R4-2006946 |
CR to 38101-3 on switching between 1Tx carrier and 2Tx carrier |
Huawei, HiSilicon |
R4-2007080 |
Clarification on the max Power between case1 and case2 |
OPPO |
R4-2008309 |
Email discussion summary for [95e][119] NR_RF_FR1_Part_2 |
Moderator (China Telecom) |
R4-2008474 |
CR to TS 38.101-1: Switching time mask between two uplink carriers in UL CA and SUL |
China Telecom, ZTE, CMCC, China Unicom, KDDI |
R4-2008475 |
CR to TS 38.101-3: Switching time mask between two uplink carriers in EN-DC |
China Telecom, ZTE, CMCC, China Unicom, KDDI |
R4-2008476 |
WF on Applicability of DL interruption for Tx switching |
China Telecom |
R4-2008949 |
Email discussion summary for [95e][119] NR_RF_FR1_Part_2 |
Moderator (China Telecom) |
R4-2009143 |
CR to TS 38.101-1: Switching time mask between two uplink carriers in UL CA and SUL |
China Telecom, ZTE, CMCC, China Unicom, KDDI |
R4-2009144 |
CR to TS 38.101-3: Switching time mask between two uplink carriers in EN-DC |
China Telecom, ZTE, CMCC, China Unicom, KDDI |
6.13.1.6 |
Transient period capability [NR_RF_FR1] |
|
R4-2007132 |
Transient Period Capability in NR using existing window definitions |
Qualcomm Incorporated, Verizon, Dish Network, Ericsson, CMCC, Keysight Technologies, Nokia, Nokia Shanghai Bell, AT&T, ZTE, Vodafone, Orange, T-Mobile USA, Deutsche Telekom, Telecom Italia, CHTTL, China Telecom, SGS Wireless, Interdigital |
R4-2007515 |
UE transient time capability |
Ericsson |
R4-2008152 |
On transient period UE capability |
Huawei, HiSilicon |
R4-2008310 |
Email discussion summary for [95e][120] NR_RF_FR1_Part_3 |
Moderator (CMCC) |
R4-2008477 |
WF on feasibility of testing the transient periods |
CMCC |
R4-2008478 |
Transient Period Capability in NR using existing window definitions |
Qualcomm Incorporated, Verizon, Dish Network, Ericsson, CMCC, Keysight Technologies, Nokia, Nokia Shanghai Bell, AT&T, ZTE, Vodafone, Orange, T-Mobile USA, Deutsche Telekom, Telecom Italia, CHTTL, China Telecom, SGS Wireless, Interdigital |
R4-2008950 |
Email discussion summary for [95e][120] NR_RF_FR1_Part_3 |
Moderator (CMCC) |
6.13.1.7 |
Time masks for ULSUP-TDM in case of UL timing misalignment [NR_RF_FR1] |
|
R4-2008245 |
Further discussion on time masks for ULSUP in R16 |
Huawei, HiSilicon |
R4-2008246 |
CR to 38.101-3 on time masks for ULSUP in R16 |
Huawei, HiSilicon |
6.13.2 |
RRM core requirements (38.133) [NR_RF_FR1] |
|
R4-2008509 |
Email discussion summary for [95e][220] NR_RF_FR1_RRM |
Moderator (Huawei, HiSilicon) |
R4-2009032 |
Email discussion summary for [95e][220] NR_RF_FR1_RRM |
Moderator (Huawei, HiSilicon) |
6.13.2.1 |
RRM requirements for Tx switching between two uplink carriers [NR_RF_FR1] |
|
R4-2006035 |
RRM interruption requirement for switching between two uplink carriers |
China Telecom |
R4-2006211 |
On DL interruption for UL Tx switching |
Apple |
R4-2006572 |
Interruption for Tx switching between two uplink carriers |
MediaTek inc. |
R4-2006805 |
RRM requirements for switching between case1 and case 2 |
CMCC |
R4-2007346 |
On interruption for FR1 Tx switching between two uplink carriers |
OPPO |
R4-2007731 |
DL interruption due to Tx switching between two uplink carriers |
Huawei, Hisilicon |
R4-2007732 |
CR on DL interruption on LTE carriers at Tx switching between two uplink carriers |
Huawei, Hisilicon |
R4-2007733 |
CR on DL interruption Tx switching between two uplink carriers |
Huawei, Hisilicon |
R4-2008623 |
WF on DL interruption on LTE carriers at Tx switching between two uplink carriers |
Huawei, HiSilicon |
R4-2008624 |
CR on DL interruption on LTE carriers at Tx switching between two uplink carriers |
Huawei, Hisilicon |
R4-2008625 |
CR on DL interruption Tx switching between two uplink carriers |
Huawei, Hisilicon |
6.14.1.1 |
FR2 MPE [NR_RF_FR2_req_enh] |
|
R4-2006311 |
Remaining issues on P-MPR reporting |
Sony, Ericsson |
R4-2006332 |
Further considerations on the uplink duty cycle enhancements for the MPE scenario |
Apple Inc. |
R4-2006510 |
UE FR2 MPE enhancements and solutions |
Nokia, Nokia Shanghai Bell |
R4-2006511 |
[Draft] LS on MPE enhancements |
Nokia, Nokia Shanghai Bell |
R4-2006579 |
Remaining details for P-MPR reporting |
InterDigital Communications |
R4-2006581 |
Introduction of P-MPR report mapping |
InterDigital Communications |
R4-2006735 |
Discussion about triggers for P-MPR reporting |
Futurewei |
R4-2006737 |
Discussion on enhancement of MPE in Rel-16 on FR2 |
LG Electronics France |
R4-2006996 |
Enhancement on FR2 MPE mitigation |
ZTE Corporation |
R4-2007081 |
Further on MPE enhancement |
OPPO |
R4-2007109 |
Views on remaining issues of Rel-16 FR2 MPE solution |
Intel Corporation |
R4-2008168 |
On MPE enhancement_FR2 |
Huawei, HiSilicon |
R4-2008311 |
Email discussion summary for [95e][121] NR_RF_FR2_req_enh_Part_1 |
Moderator (OPPO) |
R4-2008479 |
WF on MPE enhancements |
OPPO |
R4-2008480 |
[Draft] LS on MPE enhancements |
Nokia, Nokia Shanghai Bell |
R4-2008951 |
Email discussion summary for [95e][121] NR_RF_FR2_req_enh_Part_1 |
Moderator (OPPO) |
6.14.1.2 |
Beam Correspondence based on configured DL RS (SSB or CSI-RS) [NR_RF_FR2_req_enh] |
|
R4-2006319 |
Remaining issues in beam correspondence |
Sony, Ericsson |
R4-2006357 |
Remaining issues with beam correspondence in Rel-16 |
Apple Inc. |
R4-2006358 |
TP to TR38.831: beam correspondence enhancement |
Apple Inc. |
R4-2006428 |
Discussion on Rel-16 beam correspondence |
Samsung |
R4-2006429 |
CR to TS38.101-2 on Rel-16 beam correspondence |
Samsung |
R4-2006512 |
FR2 Beam Correspondence enhancements |
Nokia, Nokia Shanghai Bell |
R4-2006564 |
SSB based Beam Correspondence |
Intel Corporation |
R4-2006738 |
Discussion on enhancement of BC in Rel-16 at FR2 |
LG Electronics France |
R4-2006900 |
Views on beam correspondence enhancement based on SSB in Rel-16 |
NTT DOCOMO, INC. |
R4-2007082 |
On SSB based BC |
OPPO |
R4-2007083 |
On CSI-RS based BC |
OPPO |
R4-2007283 |
FR2 Beam Correspondence |
Qualcomm Incorporated |
R4-2008155 |
On beam correspondence enhancement |
Huawei, HiSilicon |
R4-2008178 |
LS on CSI-RS only beam correspondence |
Huawei, HiSilicon |
R4-2008205 |
Remaining details on SSB based beam correspondence |
Futurewei Technologies |
R4-2008312 |
Email discussion summary for [95e][122] NR_RF_FR2_req_enh_Part_2 |
Moderator (Apple) |
R4-2008481 |
WF on BC based on SSB |
Huawei |
R4-2008482 |
WF on BC based on CSI-RS |
Samsung |
R4-2008952 |
Email discussion summary for [95e][122] NR_RF_FR2_req_enh_Part_2 |
Moderator (Apple) |
R4-2009142 |
WF on BC based on CSI-RS |
Samsung |
R4-2009167 |
LS on CSI-RS only beam correspondence |
Huawei, HiSilicon |
6.14.1.3 |
Intra-band non-cont DL CA for aggregated BW larger than 1400 MHz [NR_RF_FR2_req_enh] |
|
R4-2006567 |
On understanding of CC allocations in FR2 intra-band non-contiguous DL CA |
Intel Corporation |
R4-2006631 |
CR to 38.101-2 on REFSENS for intra-band non-contiguous CA for FR2 |
Apple Inc. |
R4-2006632 |
[draft] LS to RAN2 on DL-only separation class |
Apple Inc. |
R4-2006634 |
CR to 38.101-2 on FR2 frequency separation class enhancement |
Apple Inc., Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R4-2006780 |
TP to TR38.831: FR2 UE architectures for DL Intra-band CA BW Enhancement |
Qualcomm Incorporated |
R4-2008154 |
On intra-band NC DL CA_FR2 |
Huawei, HiSilicon |
R4-2008177 |
CR for 38.101-2 separation class for Rel-16 |
Huawei, HiSilicon |
R4-2008313 |
Email discussion summary for [95e][123] NR_RF_FR2_req_enh_Part_3 |
Moderator (Qualcomm) |
R4-2008483 |
CR for 38.101-2 separation class for Rel-16 |
Huawei, HiSilicon |
R4-2008484 |
LS to RAN2 on DL-only separation class |
RAN4 |
R4-2008485 |
CR to 38.101-2 on FR2 frequency separation class enhancement |
Apple Inc., Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R4-2008486 |
TP to TR38.831: FR2 UE architectures for DL Intra-band CA BW Enhancement |
Qualcomm Incorporated |
R4-2008487 |
WF on FR2 inter-band DL CA |
MediaTek |
R4-2008488 |
WF on FR2 Beam Squint Effect |
Sony |
R4-2008953 |
Email discussion summary for [95e][123] NR_RF_FR2_req_enh_Part_3 |
Moderator (Qualcomm) |
R4-2009294 |
LS to RAN2 on DL-only separation class |
RAN4 |
6.14.1.4 |
Intra-band non-contiguous UL CA [NR_RF_FR2_req_enh] |
|
R4-2006361 |
Remaining issues with non-simultaneous UL for non-contiguous UL CA in FR2 |
Apple Inc. |
R4-2006486 |
FR2 intra-band non-contiguous UL CA feature |
Nokia, Qualcomm Inc. Ericsson |
R4-2006791 |
On using Rel-15 CA MPR table format for FR2 NC UL CA |
Qualcomm Incorporated |
R4-2008314 |
Email discussion summary for [95e][124] NR_RF_FR2_req_enh_Part_4 |
Moderator (Nokia) |
R4-2008489 |
WF on CA MPR table format for FR2 NC UL CA |
Qualcomm |
R4-2008890 |
FR2 intra-band non-contiguous UL CA feature |
Nokia, Qualcomm Inc. Ericsson |
R4-2008954 |
Email discussion summary for [95e][124] NR_RF_FR2_req_enh_Part_4 |
Moderator (Nokia) |
6.14.1.5 |
Inter-band DL CA [NR_RF_FR2_req_enh] |
|
R4-2006213 |
On common beam management from baseband perspective |
Apple |
R4-2006320 |
Inter-band DL CA in FR2: CBM/IBM capability and associated spherical coverage EIS tests |
Sony, Ericsson |
R4-2006430 |
on EIS relaxation framework and PSD difference in FR2 inter-band CA |
Samsung |
R4-2006565 |
Remaining issues on FR2 inter-band DL CA |
Intel Corporation |
R4-2006591 |
FR2 Inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2006592 |
TP to TR 38.831 on FR2 inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2006633 |
On common beam management assumptions and PSD difference in FR2 CA |
Apple Inc. |
R4-2006829 |
FR2 inter-band DL CA requirements |
MediaTek Inc. |
R4-2008051 |
Inter-band CA remaining open requirements |
Qualcomm Incorporated |
R4-2008052 |
DraftCR on Introduction of inter-band CA to 38.101-2 |
Qualcomm Incorporated |
R4-2008056 |
FR2 inter-band CA LB+HB |
NTT DOCOMO INC. |
R4-2008166 |
On inter band DL CA_FR2 |
Huawei, HiSilicon |
6.14.1.6 |
Improvement of UE MPR [NR_RF_FR2_req_enh] |
|
R4-2006485 |
FR2 new MPR and modifiedmpr |
Nokia, Nokia Shanghai Bell |
R4-2006782 |
FR2 UE EIRP increase with IBE relaxation |
Qualcomm Incorporated |
R4-2006783 |
LS on UL power boost mode and IBE relaxation |
Qualcomm Incorporated |
R4-2006784 |
CR to 38.101-2: FR2 UE EIRP increase with IBE relaxation |
Qualcomm Incorporated |
R4-2008891 |
FR2 new MPR and modifiedmpr |
Nokia, Nokia Shanghai Bell |
R4-2009169 |
FR2 new MPR and modifiedmpr |
Nokia, Nokia Shanghai Bell |
6.14.1.7 |
Improvement of spherical coverage requirements for PC3 [NR_RF_FR2_req_enh] |
|
R4-2006312 |
Further view on spherical coverage improvements for Rel-16 |
Samsung |
R4-2006359 |
Views on PC3 spherical coverage requirements in Rel-16 and beyond |
Apple Inc. |
R4-2007276 |
Further views on improvement to spherical coverage requirements for PC3 |
Sony |
R4-2008315 |
Email discussion summary for [95e][125] NR_RF_FR2_req_enh_Part_5 |
Moderator (Samsung) |
R4-2008892 |
WF on spherical coverage improvements and study results |
Samsung |
R4-2008955 |
Email discussion summary for [95e][125] NR_RF_FR2_req_enh_Part_5 |
Moderator (Samsung) |
6.14.1.8 |
Multiband relaxation framework enhancement [NR_RF_FR2_req_enh] |
|
R4-2006313 |
CR to 38.101-2: Revision to Multiband Relaxations |
Samsung |
R4-2006328 |
[draft] LS response on Multiband relaxation for FR2 |
Sony, Ericsson, Samsung, Qualcomm |
R4-2006350 |
Views on MBR enhancement for FR2 |
Apple Inc. |
R4-2006351 |
LS response on Multiband relaxation for FR2 |
RAN4 |
R4-2006352 |
CR to 38.101-2 on correction of the FR2 multi-band requirement framework |
Apple Inc. |
R4-2006353 |
CR to 38.307 on clarification of the FR2 multi-band requirement framework |
Apple Inc. |
R4-2006354 |
TP to TR38.831: multi-band relaxation framework enhancement |
Apple Inc. |
R4-2006365 |
CR to 38.101-2 on correction of the FR2 multi-band requirement framework |
Sony, Ericsson, Samsung, Qualcomm |
R4-2006580 |
CR to 38.101-2 on correction of the FR2 multi-band requirement framework |
Sony, Ericsson, Samsung, Qualcomm |
R4-2006707 |
MBR framework applicability |
MediaTek Beijing Inc. |
6.14.1.9 |
FR2 Beam Squint [NR_RF_FR2_req_enh] |
|
R4-2006327 |
Analysis on EIS degradation due to larger frequency separation for PC3 Ues |
Sony, Ericsson |
R4-2006781 |
Beam squint analysis for FR2 UEs |
Qualcomm Incorporated |
R4-2006842 |
Views on radiative degradation mechanisms for larger frequency separation |
Apple Inc. |
6.14.2 |
RRM core requirements (38.133) [NR_RF_FR2_req_enh] |
|
R4-2008510 |
Email discussion summary for [95e][221] NR_RF_FR2_req_enh_RRM |
Moderator (Apple) |
R4-2009033 |
Email discussion summary for [95e][221] NR_RF_FR2_req_enh_RRM |
Moderator (Apple) |
6.14.2.1 |
Inter-band DL CA MRTD [NR_RF_FR2_req_enh] |
|
R4-2006212 |
On common beam management and MRTD for FR2 iner-band CA |
Apple |
R4-2006214 |
CR on MRTD for FR2 inter-band CA |
Apple |
R4-2006215 |
CR on MRTD for FR2 inter-band CA |
Apple |
R4-2006571 |
MRTD requirements for FR2 inter-band DL CA |
MediaTek inc. |
R4-2007095 |
MRTD and MTTD requirements for FR2 inter-band DL CA |
Ericsson, , NTT DOCOMO, INC. |
R4-2007096 |
Updates on MRTD and MTTD requirements for FR2 inter-band DL CA |
Ericsson, NTT DOCOMO, INC. |
R4-2007133 |
MRTD for FR2 Inter-band CA |
Qualcomm Incorporated |
R4-2007289 |
Discussion on MRTD requirement for FR2 inter-band DL CA |
NEC |
R4-2007773 |
Discussion on MRTD requirements for FR2 inter-band DL CA |
Huawei, HiSilicon |
R4-2007774 |
CR on MRTD requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2008195 |
MRTD for inter-band DL CA |
Nokia, Nokia Shanghai Bell |
R4-2008626 |
WF on MRTD for FR2 inter-band CA |
TBA |
6.15 |
NR RRM requirement enhancement [NR_RRM_Enh_Core] |
|
R4-2008511 |
Email discussion summary for [95e][222] NR_RRM_Enh_RRM_1 |
Moderator (Intel Corporation) |
R4-2008512 |
Email discussion summary for [95e][223] NR_RRM_Enh_RRM_2 |
Moderator (ZTE) |
R4-2008513 |
Email discussion summary for [95e][224] NR_RRM_Enh_RRM_3 |
Moderator (Apple) |
R4-2008675 |
WF on NR RRM enhancements - BWP switching on multiple CCs |
Intel |
R4-2008679 |
WF on NR RRM enhancements |
MediaTek |
R4-2008685 |
WF on NR RRM enhancements |
ZTE |
R4-2008994 |
WF on NR RRM enhancements |
Apple |
R4-2008995 |
WF on NR RRM enhancements |
CMCC |
R4-2008998 |
WF on NR RRM enhancements |
Huawei |
R4-2009034 |
Email discussion summary for [95e][222] NR_RRM_Enh_RRM_1 |
Moderator (Intel Corporation) |
R4-2009035 |
Email discussion summary for [95e][223] NR_RRM_Enh_RRM_2 |
Moderator (ZTE) |
R4-2009036 |
Email discussion summary for [95e][224] NR_RRM_Enh_RRM_3 |
Moderator (Apple) |
R4-2009100 |
WF on NR RRM enhancements |
ZTE |
6.15.1.1 |
SRS carrier switching requirements [NR_RRM_Enh_Core] |
|
R4-2006474 |
Discussion on Interruption at SRS carrier switch |
MediaTek inc. |
R4-2006713 |
On SRS carrier switching requirement |
Qualcomm, Inc. |
R4-2007104 |
Interruption requirements due to SRS carrier switching |
Nokia, Nokia Shanghai Bell |
R4-2007347 |
On remaining issues for SRS carrier switching |
OPPO |
R4-2007644 |
Remaining open issues on NR SRS carrier switching RRM requirements |
ZTE |
R4-2007645 |
CR to 38.133 on SRS carrier switching interruption requirements |
ZTE |
R4-2007646 |
CR to 38.133 on impact to measurement requirements due to LTE SRS carrier switching |
ZTE |
R4-2007742 |
Discussion on SRS carrier switching interruption |
Huawei, Hisilicon |
R4-2007743 |
CR on impact on NR RRM measurement due to LTE SRS carrier switching |
Huawei, Hisilicon |
R4-2007744 |
CR on impact on LTE RRM measurement due to NR SRS carrier switching |
Huawei, Hisilicon |
R4-2007756 |
CR on NR SRS carrier switching interruption in TS 36.133 |
Huawei, Hisilicon |
R4-2008681 |
CR to 38.133 on SRS carrier switching interruption requirements |
ZTE |
R4-2008682 |
CR to 38.133 on impact to measurement requirements due to LTE SRS carrier switching |
ZTE |
R4-2008683 |
CR on impact on LTE RRM measurement due to NR SRS carrier switching |
Huawei, Hisilicon |
R4-2008684 |
CR on NR SRS carrier switching interruption in TS 36.133 |
Huawei, Hisilicon |
R4-2009128 |
CR on NR SRS carrier switching interruption in TS 36.133 |
Huawei, Hisilicon |
6.15.1.2 |
Multiple Scell activation/deactivation [NR_RRM_Enh_Core] |
|
R4-2006192 |
On remaining issues for multiple SCell activations |
Apple |
R4-2006193 |
On activation delay requirements for multiple SCell activation |
Apple |
R4-2006194 |
CR on multiple SCell activation deactivation requirement for R16 |
Apple |
R4-2006195 |
CR on multiple SCell activation interruption requirement for R16 |
Apple |
R4-2006196 |
CR on multiple NR SCell activation interruption requirement for R16 TS36.133 |
Apple |
R4-2006475 |
Discussion on Multiple SCell activation |
MediaTek inc. |
R4-2007105 |
Multiple SCells Activation Delay Requirements |
Nokia, Nokia Shanghai Bell |
R4-2007284 |
Multiple SCell activation in NR |
Qualcomm Incorporated |
R4-2007290 |
Discussion on remaining open issues in delay extension of multiple SCell activation |
NEC |
R4-2007790 |
On activation of multiple SCells |
Ericsson |
R4-2007856 |
Discussion on multiple SCell activation |
Huawei, HiSilicon |
R4-2007857 |
CR on Multiple SCell activation/deactivation delay requirements |
Huawei, HiSilicon |
R4-2007858 |
CR on Multiple SCell activation/deactivation interruption requirements 38133 |
Huawei, HiSilicon |
R4-2007859 |
CR on Multiple SCell activation/deactivation interruption requirements 36133 |
Huawei, HiSilicon |
R4-2009097 |
CR on multiple SCell activation deactivation requirement for R16 |
Apple |
R4-2009098 |
CR on multiple SCell activation interruption requirement for R16 |
Apple |
R4-2009108 |
CR on Multiple SCell activation/deactivation interruption requirements 36133 |
Huawei, HiSilicon |
6.15.1.3 |
CGI reading requirements with autonomous gap [NR_RRM_Enh_Core] |
|
R4-2006476 |
Discussion on CGI reading requirement for NR |
MediaTek inc. |
R4-2006714 |
On CGI reading requirement |
Qualcomm, Inc. |
R4-2006715 |
CR: CGI reading |
Qualcomm, Inc. |
R4-2006970 |
Further considerations for CGI decoding in NR |
Ericsson |
R4-2006971 |
LTE CGI measurements with autonomous gaps for 38.133 |
Ericsson |
R4-2006972 |
NR CGI measurements with autonomous gaps for 36.133 |
Ericsson |
R4-2007640 |
Remaining open issues on NR CGI reading with autonomous gaps |
ZTE |
R4-2007641 |
CR to 38.133 on CGI reading of NR cell |
ZTE |
R4-2007642 |
CR to 38.133 on interruption requirements for CGI reading |
ZTE |
R4-2007643 |
Reply LS on CGI reading with autonomous gaps |
ZTE |
R4-2007860 |
Discussion on NR CGI reading requirements |
Huawei, HiSilicon |
R4-2007861 |
Discussion on scope and requirements for LTE CGI reading |
Huawei, HiSilicon |
R4-2007862 |
CR to 36.133 on interruption requirements for CGI reading |
Huawei, HiSilicon |
R4-2007863 |
CR to 36.133 on CGI reading of LTE cell |
Huawei, HiSilicon |
R4-2008188 |
discussion on CGI reading with autonomous gap |
Nokia, Nokia Shanghai Bell |
R4-2008189 |
Draft Response LS on CGI reading with autonomous gaps |
Nokia, Nokia Shanghai Bell |
R4-2008686 |
Reply LS on CGI reading with autonomous gaps |
ZTE |
R4-2008687 |
LTE CGI measurements with autonomous gaps for 38.133 |
Ericsson |
R4-2008688 |
NR CGI measurements with autonomous gaps for 36.133 |
Ericsson |
R4-2008689 |
CR to 38.133 on CGI reading of NR cell |
ZTE |
R4-2008990 |
CR to 38.133 on interruption requirements for CGI reading |
ZTE |
R4-2008991 |
CR to 36.133 on interruption requirements for CGI reading |
Huawei, HiSilicon |
R4-2009268 |
Reply LS on CGI reading with autonomous gaps |
RAN4 |
6.15.1.4 |
BWP switching on multiple CCs [NR_RRM_Enh_Core] |
|
R4-2006203 |
Discussion on requirements for BWP switching on multiple CCs |
Apple |
R4-2006477 |
Discussion on BWP switch on multiple CC |
MediaTek inc. |
R4-2006522 |
Remaining issues on BWP switching on mulitple CCs |
vivo |
R4-2006551 |
Discussion on RRM requirements for BWP switching on multiple CCs |
Intel Corporation |
R4-2007291 |
Discussion on requirements for BWP switch delay on multiple CC |
NEC |
R4-2007348 |
On RRM requirements for BWP switching on multiple CCs |
OPPO |
R4-2007498 |
Delay requirement for simultaneous switching of multiple BWPs |
Qualcomm |
R4-2007680 |
CR on introduction of RRM requirements for BWP switching delay on multiple CCs |
Huawei, Hisilicon |
R4-2007681 |
Discussion on partial overlap BWP switching on multiple CCs |
Huawei, Hisilicon |
R4-2007682 |
Discussion on simultaneous BWP switching on multiple CCs |
Huawei, Hisilicon |
R4-2007788 |
On simultaneous BWP switching on multiple CCs |
Ericsson |
R4-2007990 |
Analysis of open issues for partially overlapped BWP triggering on multiple CCs |
Ericsson |
R4-2008190 |
discussion on BWP switch on multiple CCs |
Nokia, Nokia Shanghai Bell |
R4-2008191 |
CR on 36133 interruption requirements for BWP switching on multiple CCs |
Nokia, Nokia Shanghai Bell |
R4-2008192 |
CR on 38133 interruption requirements for BWP switching on multiple CCs |
Nokia, Nokia Shanghai Bell |
R4-2008676 |
CR on introduction of RRM requirements for BWP switching delay on multiple CCs |
Huawei, Hisilicon |
R4-2008677 |
CR on 36133 interruption requirements for BWP switching on multiple CCs |
Nokia, Nokia Shanghai Bell |
R4-2008678 |
CR on 38133 interruption requirements for BWP switching on multiple CCs |
Nokia, Nokia Shanghai Bell |
6.15.1.5 |
Inter-frequency measurement requirement without MG [NR_RRM_Enh_Core] |
|
R4-2006521 |
Remaining issues for inter-frequency measurement without gap |
vivo |
R4-2006716 |
On Inter-frequency without gap requirement |
Qualcomm, Inc. |
R4-2006806 |
RRM requirements on inter-frequency measurement without gap |
CMCC |
R4-2006807 |
CR on introducing inter-frequency measurements without measurement gap (9.1.5, 9.1.6, 9.3.1, 9.3.4, 9.3.5) |
CMCC |
R4-2006888 |
Discussion on inter-frequency measurement requirement without gap |
MediaTek inc. |
R4-2007349 |
On remaining issues for inter-frequency measurement without MG |
OPPO |
R4-2007745 |
LS on inter-frequency measurement requirement without MG |
RAN4 |
R4-2007746 |
Discussion on inter-frequency measurement without gap |
Huawei, Hisilicon |
R4-2008996 |
CR on introducing inter-frequency measurements without measurement gap (9.1.5, 9.1.6, 9.3.1, 9.3.4, 9.3.5) |
CMCC |
6.15.1.6 |
Mandatory MG patterns [NR_RRM_Enh_Core] |
|
R4-2006717 |
On Mandatory gap patterns requirement |
Qualcomm, Inc. |
R4-2006718 |
CR: mandatory gap pattern |
Qualcomm, Inc. |
R4-2006767 |
Further discussion on mandating gap patterns for Rel-16 NR |
CMCC |
R4-2006874 |
Discussion on mandatory MG patterns |
NTT DOCOMO, INC. |
R4-2006974 |
Further discussion on additional mandatory gap patterns for release 16 |
Ericsson |
R4-2006975 |
Further LS on mandatory of measurement gap patterns |
Ericsson |
R4-2007159 |
Discussion on Mandatory Gap Patterns |
Nokia, Nokia Shanghai Bell |
R4-2007350 |
On remaining issues for mandatory MG patterns |
OPPO |
R4-2007647 |
LS on mandatory of measurement gap patterns |
ZTE |
R4-2007648 |
Remaining open issues on mandatary gap patterns |
ZTE |
R4-2007747 |
Discussion on mandatory gap pattern in R-16 |
Huawei, Hisilicon |
R4-2007748 |
[Draft] LS on mandantory gap patterns |
Huawei, Hisilicon |
R4-2008992 |
LS on mandatory of measurement gap patterns |
ZTE |
R4-2008993 |
CR: mandatory gap pattern |
CMCC |
R4-2009269 |
LS on mandatory of measurement gap patterns |
RAN4 |
6.15.1.7 |
UE-specific CBW change [NR_RRM_Enh_Core] |
|
R4-2006197 |
CR on UE behavior for UE specific CBW change |
Apple |
R4-2006547 |
CR to TS 38.133: RRM requirement for UE-specific CBW change delay |
Intel Corporation |
R4-2006548 |
CR to TS 38.133: RRM requirement for interruption due to UE-specific CBW change |
Intel Corporation |
R4-2009124 |
CR to TS 38.133: RRM requirement for UE-specific CBW change delay |
Intel Corporation |
6.15.1.8 |
Spatial relation switch for uplink [NR_RRM_Enh_Core] |
|
R4-2006204 |
Discussion on requirements for UL spatial relation info switch |
Apple |
R4-2006478 |
Discussion on active spatial relation switch |
MediaTek inc. |
R4-2006479 |
CR on active spatial relation switch |
MediaTek inc. |
R4-2006554 |
Discussion on requirements for spatial relation info switch for UL |
Intel Corporation |
R4-2006875 |
Discussion on spatial relation switch for uplink |
NTT DOCOMO, INC. |
R4-2007160 |
Discussion on UL spatial relation switch |
Nokia, Nokia Shanghai Bell |
R4-2007496 |
Spatial relation switch for uplink |
Qualcomm |
R4-2007749 |
Discussion on spatial relation switch for uplink channels and SRS |
Huawei, Hisilicon |
R4-2007789 |
On spatial relation switching delay requirements |
Ericsson |
R4-2008680 |
CR on active spatial relation switch |
MediaTek inc. |
6.15.1.10 |
Inter-band CA requirement for FR2 UE measurement capability of independent Rx beam and/or common beam [NR_RRM_Enh_Core] |
|
R4-2006869 |
Discussion on Inter-band CA requirement for FR2 |
MediaTek inc. |
R4-2006876 |
Discussion on inter-band CA requirement for FR2 |
NTT DOCOMO, INC. |
R4-2006973 |
RRM requirements for interband FR2 operation |
Ericsson |
R4-2007161 |
FR2 inter-band CA requirement |
Nokia, Nokia Shanghai Bell |
R4-2007497 |
RRM requirements with common and independent beams in FR2 inter band CA |
Qualcomm |
R4-2007775 |
Discussion on RRM requirements of FR2 inter-band CA scenario |
Huawei, HiSilicon |
R4-2007776 |
CR on interruption requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2007777 |
CR on scaling factor CSSFoutside_gap for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2007778 |
CR on scheduling availability requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2007779 |
CR on measurement restriction requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2007802 |
CR on SCell activation requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2008999 |
CR on interruption requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2009000 |
CR on scheduling availability requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2009001 |
CR on measurement restriction requirements for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2009118 |
CR on SCell activation requirements for FR2 inter-band CA |
Huawei, HiSilicon |
6.16 |
NR RRM requirements for CSI-RS based L3 measurement [NR_CSIRS_L3meas] |
|
R4-2008514 |
Email discussion summary for [95e][225] NR_CSIRS_L3meas_RRM_1 |
Moderator (CATT) |
R4-2008515 |
Email discussion summary for [95e][226] NR_CSIRS_L3meas_RRM_2 |
Moderator (OPPO) |
R4-2009002 |
WF on CSI-RS configuration and intra/inter-frequency measurements definition for CSI-RS based L3 measurement |
CATT |
R4-2009009 |
WF on CSI-RS based L3 measurement capability and requirements |
OPPO |
R4-2009010 |
CR on Carrier-specific scaling factor for CSI-RS measurements |
MediaTek |
R4-2009011 |
CR on L3 CSI-RS measurements introduction, requirement applicability and number of cells/beams to be measured for inter-frequency measurement |
vivo |
R4-2009012 |
CR on scheduling restriction for CSI-RS based intra-frequency measurement |
Qualcomm |
R4-2009037 |
Email discussion summary for [95e][225] NR_CSIRS_L3meas_RRM_1 |
Moderator (CATT) |
R4-2009038 |
Email discussion summary for [95e][226] NR_CSIRS_L3meas_RRM_2 |
Moderator (OPPO) |
R4-2009256 |
WF on CSI-RS configuration and intra/inter-frequency measurements definition for CSI-RS based L3 measurement |
CATT |
6.16.1 |
RRM core requirements (38.133) [NR_CSIRS_L3meas-Core] |
|
R4-2006216 |
On remaining issues for CSI-RS based L3 measurements |
Apple |
6.16.1.1 |
CSI-RS measurement bandwidth [NR_CSIRS_L3meas-Core] |
|
R4-2006223 |
Discussion on the remaining issues on CSI-RS measurement configuration and definition for RRM measurement requirement |
CATT |
R4-2006949 |
Discussion on CSI-RS parameters for RRM core requirements |
NTT DOCOMO, INC. |
R4-2007098 |
Discussion on CSI-RS measurement bandwidth |
Nokia, Nokia Shanghai Bell |
R4-2007649 |
Further discussion on configuration of CSI-RS based L3 measurement |
ZTE |
R4-2007803 |
Discussion on CSI-RS L3 measurement period requirements |
Huawei, HiSilicon |
6.16.1.2 |
CSI-RS based intra-frequency and inter-frequency measurements definition [NR_CSIRS_L3meas-Core] |
|
R4-2006224 |
LS on CSI-RS based intra-frequency and inter-frequency Measurement definition |
CATT |
R4-2006553 |
Discussion about CSI-RS L3 measurement bandwidth and definition |
Intel Corporation |
R4-2006573 |
Definition of Intra and inter frequency for CSI-RS RRM |
MediaTek inc. |
R4-2006763 |
Further discussion on the definition of CSI-RS based intra-frequency measurements |
CMCC |
R4-2006950 |
Discussion on the definition of CSI-RS based intra-frequency and inter-frequency measurement |
NTT DOCOMO, INC. |
R4-2007099 |
CSI-RS based intra-frequency measurements definition |
Nokia, Nokia Shanghai Bell |
R4-2007292 |
Definition of Intra and Inter-frequency CSI-RS based L3 measurements |
NEC |
R4-2007351 |
On remaining issues for definition of intra-f CSI-RS L3 measurement |
OPPO |
R4-2007651 |
Further discussion on definition of CSI-RS based RRM measurements |
ZTE |
R4-2007734 |
Definition for the CSI-RS based intra-frequency and inter-frequency measurement |
Huawei, Hisilicon |
R4-2007735 |
[DRAFT] Reply LS on clarification about CSI-RS measurement |
Huawei, Hisilicon |
R4-2007737 |
CR on CSI-RS based L3 measurement framework and introduction |
Huawei, Hisilicon |
R4-2007738 |
CR on CSI-RS based intra-f and inter-f measurement definition |
Huawei, Hisilicon |
R4-2008143 |
More comments on CSI-RS based intra-frequency and inter-frequency measurements definition |
Qualcomm CDMA Technologies |
R4-2009003 |
LS on CSI-RS based intra-frequency and inter-frequency Measurement definition |
CATT |
R4-2009004 |
CR on CSI-RS based L3 measurement framework and introduction |
Huawei, Hisilicon |
R4-2009134 |
LS on CSI-RS based intra-frequency and inter-frequency Measurement definition |
CATT |
R4-2009260 |
LS on CSI-RS based intra-frequency and inter-frequency Measurement definition |
RAN4 |
6.16.1.3 |
Measurement capability [NR_CSIRS_L3meas-Core] |
|
R4-2006225 |
Further discussion on CSI-RS based UE measurement capabilities |
CATT |
R4-2006227 |
CR on CSI-RS based UE measurement capabilities |
CATT |
R4-2006552 |
Discussion about CSI-RS L3 measurement capability and requirements |
Intel Corporation |
R4-2006574 |
Discussion on measurement capability for CSI-RS RRM |
MediaTek inc. |
R4-2006764 |
Further discussion on CSI-RS measurement capability |
CMCC |
R4-2006766 |
38.133 CR on UE measurement capability for CSI-RS measurement |
CMCC |
R4-2007100 |
Discussion on the CSI-RS based measurement capability |
Nokia, Nokia Shanghai Bell |
R4-2007352 |
On Measurement capability for CSI-RS L3 measurement |
OPPO |
R4-2007353 |
Draft CR on CSI-RS based L3 measurement capability(9.1.3) |
OPPO |
R4-2007354 |
Draft CR on CSI-RS based L3 measurement capability(9.2.3) |
OPPO |
R4-2007355 |
Draft CR on CSI-RS based L3 measurement capability(9.3.3) |
OPPO |
R4-2007650 |
Further discussion on UE measurement capability of CSI-RS based RRM measurements |
ZTE |
R4-2007864 |
On CSI-RS measurement capability |
Huawei, HiSilicon |
R4-2007865 |
CR on CSI-RS measurement capability - number of cells and beams |
Huawei, HiSilicon |
R4-2007866 |
CR on CSI-RS measurement capability - number of layers |
Huawei, HiSilicon |
R4-2007867 |
On time window for CSI-RS measurement |
Huawei, HiSilicon |
R4-2008237 |
More comments on CSI-RS measurement capabilities and requirements |
Qualcomm CDMA Technologies |
R4-2009005 |
38.133 CR on UE measurement capability for CSI-RS measurement |
CMCC |
6.16.1.4 |
Intra-frequency and inter-frequency measurement requirements [NR_CSIRS_L3meas-Core] |
|
R4-2006226 |
Discussion on CSI-RS based measurement requirements |
CATT |
R4-2006228 |
CR on Carrier-specific scaling factor for CSI-RS measurement |
CATT |
R4-2006229 |
CR on CSI-RS based intra-frequency measurement requirement |
CATT |
R4-2006230 |
CR on CSI-RS based inter-frequency measurement requirement |
CATT |
R4-2006575 |
Cell identification requirements for CSI-RS RRM |
MediaTek inc. |
R4-2006765 |
Discussion on CSI-RS measurement requirements |
CMCC |
R4-2006841 |
Discussion on CSI-RS L3 measurement requirement |
LG Electronics Inc. |
R4-2006951 |
Discussion on measurement requirements of CSI-RS based L3 measurement |
NTT DOCOMO, INC. |
R4-2007101 |
CSI-RS based intra-frequency measurement requirements |
Nokia, Nokia Shanghai Bell |
R4-2007356 |
On measurement requirement for CSI-RS based L3 measurements |
OPPO |
R4-2007357 |
Draft CR on intra-frequency CSI-RS L3 measurement(9.2.1, 9.2.4) |
OPPO |
R4-2007358 |
Draft CR on intra-frequency CSI-RS L3 measurement requirement(9.2.5) |
OPPO |
R4-2007359 |
Draft CR on inter-frequency CSI-RS L3 measurements(section 9.3.1, 9.3.6) |
OPPO |
R4-2007360 |
Draft CR on inter-frequency CSI-RS L3 measurements requirement(section 9.3.4, 9.3.5) |
OPPO |
R4-2007736 |
Discussion on CSI-RS based L3 measurement requirements |
Huawei, Hisilicon |
R4-2007739 |
CR on CSI-RS based measurement requirements |
Huawei, Hisilicon |
R4-2009006 |
CR on CSI-RS based intra-frequency measurement requirement |
CATT |
R4-2009007 |
CR on CSI-RS based measurement requirements |
Huawei, Hisilicon |
R4-2009008 |
Draft CR on intra-frequency CSI-RS L3 measurement requirement(9.2.5) |
OPPO |
R4-2009099 |
CR on inter-frequency CSI-RS L3 measurement requirement (9.2.5) |
OPPO |
6.16.1.5 |
Others [NR_CSIRS_L3meas-Core] |
|
R4-2006576 |
Synchronization assumption for L3 CSI-RS measurement |
MediaTek inc. |
R4-2007102 |
Pre-emption on CSI-RS based measurements |
Nokia, Nokia Shanghai Bell |
R4-2007103 |
Simulation results for CSI-RS based measurements |
Nokia, Nokia Shanghai Bell |
R4-2007868 |
On synchronization assumption for CSI-RS measurement requirements |
Huawei, HiSilicon |
6.17.1 |
RRM core requirements (38.133) [NR_HST-Core] |
|
R4-2006719 |
On HST RRM requirement |
Qualcomm, Inc. |
R4-2006770 |
Further discussion on RRM for NR high speed scenario |
CMCC |
R4-2006772 |
Discussion on SS-SINR measurement for NR HST |
CMCC |
R4-2006965 |
LS on supporting Rel-16 NR HST RRM enhanced requirements from Rel-15 UEs |
RAN4 |
R4-2007272 |
Discussion on remaining RRM issues in NR HST |
vivo |
R4-2008516 |
Email discussion summary for [95e][227] NR_HST_RRM |
Moderator (CMCC) |
R4-2008627 |
WF on NR HST RRM requirements |
CMCC |
R4-2009039 |
Email discussion summary for [95e][227] NR_HST_RRM |
Moderator (CMCC) |
6.17.1.1 |
Cell re-selection [NR_HST-Core] |
|
R4-2006774 |
38.133 CR on cell re-selection requirements for Rel-16 NR HST |
CMCC |
R4-2007162 |
NR HST Serving cell and idle mode |
Nokia, Nokia Shanghai Bell |
R4-2008040 |
CR for Measurement and evaluation of serving cell in HST |
Nokia Corporation |
R4-2008628 |
38.133 CR on cell re-selection requirements for Rel-16 NR HST |
CMCC |
6.17.1.2 |
Cell identification delay [NR_HST-Core] |
|
R4-2006231 |
CR on cell identification requirements for NR HST |
CATT |
R4-2006983 |
Requirement applicability in NR high speed |
Ericsson |
R4-2007163 |
Connected mode HST operation with long DRX |
Nokia, Nokia Shanghai Bell |
R4-2008090 |
Discussions on SS-SINR measurements for Rel-16 high speed train |
Nokia, Nokia Shanghai Bell |
R4-2008629 |
CR on cell identification requirements for NR HST |
CATT |
6.17.1.3 |
RLM [NR_HST-Core] |
|
R4-2008058 |
CR to TS 38.133: NR HST RLM requirements |
Nokia, Nokia Shanghai Bell |
R4-2008630 |
CR to TS 38.133: NR HST RLM requirements |
Nokia, Nokia Shanghai Bell |
6.17.1.4 |
Beam management [NR_HST-Core] |
|
R4-2008065 |
CR to TS 38.133: NR HST beam management requirements |
Nokia, Nokia Shanghai Bell |
R4-2008631 |
CR to TS 38.133: NR HST beam management requirements |
Nokia, Nokia Shanghai Bell |
6.17.1.5 |
Inter-RAT measurement [NR_HST-Core] |
|
R4-2006771 |
Further discussion on inter-RAT measurement requirements for NR HST |
CMCC |
R4-2006773 |
36.133 CR on cell identification in connected mode for |
CMCC |
R4-2006984 |
InterRAT requirements for high speed train |
Ericsson |
R4-2006985 |
Cell re-selection for EUTRAN-NR high speed in TS36.133 |
Ericsson |
R4-2007164 |
Idle mode inter-RAT measurements requirements |
Nokia, Nokia Shanghai Bell |
R4-2007165 |
Connected mode inter-RAT measurements |
Nokia, Nokia Shanghai Bell |
R4-2007273 |
CR on cell re-selection requirement for NR-EUTRAN measurement in TS38.133 |
vivo |
R4-2007740 |
Discussion on the RRM requirements in NR HST |
Huawei, Hisilicon |
R4-2007741 |
Cell identification in connected mode for NR-EUTRAN measurement in HST |
Huawei, Hisilicon |
R4-2008632 |
36.133 CR on cell identification in connected mode for |
CMCC |
R4-2008633 |
Cell re-selection for EUTRAN-NR high speed in TS36.133 |
Ericsson |
R4-2008634 |
CR on cell re-selection requirement for NR-EUTRAN measurement in TS38.133 |
vivo |
R4-2008635 |
Cell identification in connected mode for NR-EUTRAN measurement in HST |
Huawei, Hisilicon |
R4-2009240 |
Cell re-selection for EUTRAN-NR high speed in TS36.133 |
Ericsson |
6.17.2 |
Demodulation and CSI requirements (38.101-4 / 38.104) [NR_HST-Perf] |
|
R4-2008710 |
Email discussion summary for [95e][321] NR_HST_Demod_UE |
Moderator (CMCC) |
R4-2008711 |
Email discussion summary for [95e][322] NR_HST_Demod_BS |
Moderator (Nokia) |
R4-2008820 |
WF on NR HST demodulation requirements |
CMCC |
R4-2008821 |
WF on Rel-16 NR HST BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2009041 |
Email discussion summary for [95e][321] NR_HST_Demod_UE |
Moderator (CMCC) |
R4-2009042 |
Email discussion summary for [95e][322] NR_HST_Demod_BS |
Moderator (Nokia) |
R4-2009052 |
Summary of ideal and impairment results for NR HST demodulation requirements |
Huawei |
6.17.2.1 |
UE demodulation and CSI requirements (38.101-4) [NR_HST-Perf] |
|
R4-2006612 |
Views on Tests for High Speed Train Scenarios |
Qualcomm Incorporated |
R4-2006768 |
Further discussion on UE demodulation for NR HST |
CMCC |
R4-2007137 |
Views on applicability rule for HST demodulation requirements |
NTT DOCOMO, INC. |
R4-2007234 |
Discussion on general issues for NR UE HST performance requirements |
Huawei, HiSilicon |
R4-2007274 |
Discussion on UE demodulation requirements for NR HST |
vivo |
R4-2007384 |
Release independence and applicability rule for NR HST demodulation requirements |
Ericsson |
R4-2007921 |
Addition of Rel-16 HST FRC |
Ericsson |
R4-2008819 |
Addition of Rel-16 HST FRC |
Ericsson |
6.17.2.1.1 |
Scenarios and transmission schemes [NR_HST-Perf] |
|
R4-2006534 |
Views on DL demodulation requirements for DPS transmission scheme |
Intel Corporation |
R4-2007233 |
Discussion on UE performance requirements for DPS transmission scheme |
Huawei, HiSilicon |
R4-2007382 |
Transmission scheme in NR PDSCH demodulation requirements for HST |
Ericsson |
6.17.2.1.2 |
Requirements for HST-SFN [NR_HST-Perf] |
|
R4-2006535 |
Views on NR UE demodulation requirements for HST-SFN scenario |
Intel Corporation |
R4-2007135 |
Views on HST-SFN |
NTT DOCOMO, INC. |
R4-2007235 |
Discussion and simulation results on NR UE HST performance requirements for SFN |
Huawei, HiSilicon |
6.17.2.1.3 |
Requirements for HST single tap [NR_HST-Perf] |
|
R4-2006536 |
Views on NR UE demodulation requirements for HST single tap scenario |
Intel Corporation |
R4-2007136 |
Views on HST single-tap |
NTT DOCOMO, INC. |
R4-2007236 |
Discussion and simulation results on NR UE HST performance requirements for single-tap |
Huawei, HiSilicon |
R4-2007383 |
Discussion on PDSCH demodulation performance with HST single tap |
Ericsson |
R4-2007923 |
Simulation results for NR UE HST single tap |
Ericsson |
6.17.2.1.4 |
Requirements for multi-path fading channels [NR_HST-Perf] |
|
R4-2006537 |
Simulation results for HST multi-path fading channel scenario |
Intel Corporation |
R4-2007237 |
Simulation results on NR UE HST performance requirements for multi-path fading channel |
Huawei, HiSilicon |
R4-2007922 |
Simulation results for HST Multipath fading channels |
Ericsson |
6.17.2.1.5 |
Network assistance and UE capability signalling [NR_HST-Perf] |
|
R4-2006538 |
Views on UE demodulation requirements for NR HST |
Intel Corporation |
6.17.2.2 |
BS demodulation requirements (38.104) [NR_HST-Perf] |
|
R4-2006254 |
Summary of ideal and impairment results for NR HST demodulation requirements |
CATT |
R4-2006266 |
Discussion on high speed support declaration for NR HST |
CATT |
R4-2006267 |
Discussion on multi-path fading channel for NR HST |
CATT |
R4-2006270 |
CR for TS 38.141-1, Introduction of high speed support declaration for NR HST |
CATT |
R4-2006271 |
CR for TS 38.141-2, Introduction of high speed support declaration for NR HST |
CATT |
R4-2006769 |
Discussion on BS demodulation for NR HST |
CMCC |
R4-2008822 |
Summary of ideal and impairment results for NR HST demodulation requirements |
CATT |
R4-2008871 |
CR for TS 38.141-1, Introduction of high speed support declaration for NR HST |
CATT |
R4-2008872 |
CR for TS 38.141-2, Introduction of high speed support declaration for NR HST |
CATT |
R4-2009058 |
CR for TS 38.141-2, Introduction of high speed support declaration for NR HST |
CATT |
6.17.2.2.1 |
PUSCH requirements [NR_HST-Perf] |
|
R4-2006052 |
On NR Rel-16 HST BS demodulation PUSCH requirements |
Nokia, Nokia Shanghai Bell |
R4-2006053 |
CR for 38.104: HST PUSCH demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2006054 |
CR for 38.104: HST PUSCH demodulation FRC and channel model annexes |
Nokia, Nokia Shanghai Bell |
R4-2006258 |
Simulation results for NR HST PUSCH demodulation requirement |
CATT |
R4-2006265 |
Discussion on 1T1R for tunnel scenario for NR HST PUSCH |
CATT |
R4-2006268 |
Discussion on the introduction of DFT-s-OFDM for NR HST PUSCH |
CATT |
R4-2006323 |
Discussion and simulation results for NR HST PUSCH |
Samsung |
R4-2006666 |
Further discussion on HST PUSCH BS demodulation requirements |
ZTE Wistron Telecom AB |
R4-2006833 |
Discussion on HST PUSCH remain isses |
Ericsson |
R4-2006836 |
Introduction of conformance tests for 350kph and 500kph HST |
Ericsson |
R4-2006837 |
HST PUSCH demodulation FRC and channel condition annex |
Ericsson |
R4-2007182 |
Views on NR PUSCH for high speed |
NTT DOCOMO, INC. |
R4-2007183 |
CR for TS 38.141-1: Introduction of NR PUSCH performance requirements for HST |
NTT DOCOMO, INC. |
R4-2007184 |
CR for TS 38.141-1: Introduction of NR PUSCH performance Annex including FRC and channel model for HST |
NTT DOCOMO, INC. |
R4-2007231 |
Discussion and simulation results on the NR HST PUSCH performance requirements |
Huawei, HiSilicon |
R4-2007422 |
Views on PUSCH demodulation requirements for HST multi-path fading channel conditions |
Intel Corporation |
R4-2007423 |
PUSCH simulation results for HST tunnel scenario |
Intel Corporation |
R4-2008206 |
Simulation results for NR HST PUSCH performance requirements |
Huawei, HiSilicon |
R4-2008823 |
CR for 38.104: HST PUSCH demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2008824 |
CR for 38.104: HST PUSCH demodulation FRC and channel model annexes |
Nokia, Nokia Shanghai Bell |
R4-2008825 |
Introduction of conformance tests for 350kph and 500kph HST |
Ericsson |
R4-2008826 |
HST PUSCH demodulation FRC and channel condition annex |
Ericsson |
R4-2008827 |
CR for TS 38.141-1: Introduction of NR PUSCH performance requirements for HST |
NTT DOCOMO, INC. |
R4-2008828 |
CR for TS 38.141-1: Introduction of NR PUSCH performance Annex including FRC and channel model for HST |
NTT DOCOMO, INC. |
6.17.2.2.2 |
PRACH requirements [NR_HST-Perf] |
|
R4-2006055 |
On NR Rel-16 HST BS demodulation PRACH requirements |
Nokia, Nokia Shanghai Bell |
R4-2006667 |
Further discussion on HST PRACH BS demodulation requirements |
ZTE Wistron Telecom AB |
R4-2006834 |
Discussion on HST PRACH remain isses |
Ericsson |
R4-2007185 |
Views on NR PRACH for high speed |
NTT DOCOMO, INC. |
R4-2007204 |
CR for 38.104 Introduction of PRACH demodulation requirements for NR HST |
Huawei, HiSilicon |
R4-2007205 |
CR for 38.141-1 Introduction of PRACH conducted conformance testing for NR HST |
Huawei, HiSilicon |
R4-2007206 |
CR for 38.141-2 Introduction of PRACH radiated conformance testing for NR HST |
Huawei, HiSilicon |
R4-2007207 |
Discussion on open issues of NR HST PRACH |
Huawei, HiSilicon |
R4-2008829 |
CR for 38.104 Introduction of PRACH demodulation requirements for NR HST |
Huawei, HiSilicon |
R4-2008830 |
CR for 38.141-1 Introduction of PRACH conducted conformance testing for NR HST |
Huawei, HiSilicon |
R4-2008831 |
CR for 38.141-2 Introduction of PRACH radiated conformance testing for NR HST |
Huawei, HiSilicon |
6.17.2.2.3 |
UL timing adjustment requirements [NR_HST-Perf] |
|
R4-2006056 |
On NR Rel-16 HST BS demodulation UL timing adjustment requirements |
Nokia, Nokia Shanghai Bell |
R4-2006255 |
CR for TS 38.141-2: introduction of NR PUSCH UL timing adjustment |
CATT |
R4-2006256 |
CR for TS 38.141-2: appendix for NR PUSCH UL timing adjustment |
CATT |
R4-2006257 |
Simulation results for NR PUSCH UL timing adjustment demodulation requirement |
CATT |
R4-2006269 |
Discussion on the remaining issues of NR HST PUSCH UL TA |
CATT |
R4-2006321 |
CR on UL timing adjustment conducted performance requirement for TS 38.141-1 |
Samsung |
R4-2006322 |
CR on FRC and moving progagation condition for UL timing adjustment for TS 38.141-1 |
Samsung |
R4-2006324 |
Discussion and simulation results for NR HST UL timing requirement |
Samsung |
R4-2006664 |
CR for 38.104: Performance requirements for UL timing adjustment |
ZTE Wistron Telecom AB |
R4-2006665 |
Further discussion on BS demodulation performance requirements for UL TA |
ZTE Wistron Telecom AB |
R4-2006835 |
Discussion on HST UL TA remain isses |
Ericsson |
R4-2007186 |
Views on NR PUSCH for UL timing adjustment |
NTT DOCOMO, INC. |
R4-2007232 |
Discussion and simulation results on the NR HST UL timing performance requirements |
Huawei, HiSilicon |
R4-2008832 |
CR for TS 38.141-2: introduction of NR PUSCH UL timing adjustment |
CATT |
R4-2008833 |
CR for TS 38.141-2: appendix for NR PUSCH UL timing adjustment |
CATT |
R4-2008834 |
CR on UL timing adjustment conducted performance requirement for TS 38.141-1 |
Samsung |
R4-2008835 |
CR on FRC and moving progagation condition for UL timing adjustment for TS 38.141-1 |
Samsung |
R4-2008836 |
CR for 38.104: Performance requirements for UL timing adjustment |
ZTE Wistron Telecom AB |
6.18 |
NR performance requirement enhancement [NR_perf_enh-Perf] |
|
R4-2006036 |
Updated CR work split for NR performance requirement enhancement WI |
China Telecom |
R4-2008712 |
Email discussion summary for [95e][323] NR_perf_enh_Demod_UE |
Moderator (China Telecomm) |
R4-2008713 |
Email discussion summary for [95e][324] NR_perf_enh_Demod_BS |
Moderator (CATT) |
R4-2008837 |
Way forward on release independent aspect for UE demodulation and CSI reporting requirements |
Huawei |
R4-2008838 |
Way forward on PDSCH CA normal demodulation requirements |
Intel |
R4-2008839 |
Simulation assumptions for NR normal CA UE performance requirements |
Intel |
R4-2008840 |
Summary of Normal CA simulation results (FR1 15 kHz FDD and TDD) |
Intel |
R4-2008841 |
Summary of Normal CA simulation results (FR1 30 kHz TDD) |
Intel |
R4-2008846 |
Way forward on PMI reporting requirements for Tx ports larger than 8 and up to 32 |
Ericsson, Samsung |
R4-2008847 |
Simulation assumptions for NR PMI reporting requirements for more than 8 Tx ports |
Ericsson |
R4-2008848 |
Way forward on UE power imbalance requirements for FR1 CA and EN-DC |
NTT DoCoMo |
R4-2008849 |
Way forward on CA CQI reporting requirements |
China Telecom |
R4-2009043 |
Email discussion summary for [95e][323] NR_perf_enh_Demod_UE |
Moderator (China Telecomm) |
R4-2009044 |
Email discussion summary for [95e][324] NR_perf_enh_Demod_BS |
Moderator (CATT) |
6.18.1 |
UE demodulation and CSI requirements (38.101-4) [NR_perf_enh-Perf] |
|
R4-2007220 |
Discussion on Release independent aspects for UE demod and CSI reporting requirements |
Huawei, HiSilicon |
6.18.1.1 |
NR CA PDSCH requirements [NR_perf_enh-Perf] |
|
R4-2006037 |
On NR CA PDSCH normal demodulation requirements |
China Telecom |
R4-2006530 |
Discussion on NR CA UE demodulation requirements |
Intel Corporation |
R4-2006531 |
Summary of Normal CA simulation results (FR2) |
Intel Corporation |
R4-2006628 |
Simulation Results for NR CA PDSCH Demodulation Performance Tests |
Qualcomm Incorporated |
R4-2006629 |
Views on NR CA PDSCH Demodulation Performance Tests |
Qualcomm Incorporated |
R4-2006808 |
Test applicability rule for NR CA PDSCH normal demodulation |
CMCC |
R4-2007139 |
Views on PDSCH CA normal demodulation requirements |
NTT DOCOMO, INC. |
R4-2007221 |
Discussion on HARQ timing for NR UE normal CA performance requirements |
Huawei, HiSilicon |
R4-2007222 |
Discussion on PDSCH CA normal demodulation requirements |
Huawei, HiSilicon |
R4-2007223 |
draftCR for NR FR1 PDSCH CA normal demodulation requirements with 4Rx |
Huawei, HiSilicon |
R4-2008842 |
draftCR for NR FR1 PDSCH CA normal demodulation requirements with 4Rx |
Huawei, HiSilicon |
6.18.1.2 |
PMI reporting requirements with larger number of Tx ports [NR_perf_enh-Perf] |
|
R4-2006038 |
On PMI reporting requirements with larger number of Tx ports |
China Telecom |
R4-2006318 |
Views and simulation results for PMI test cases |
Samsung |
R4-2006615 |
Parameters and simulation results on PMI reporting requirements with larger number of Tx ports |
Qualcomm Incorporated |
R4-2007201 |
Simulation results for Single Panel Type I PMI reporting test with larger Tx ports |
Huawei, HiSilicon |
R4-2007202 |
Discussion on open issues for Type II codebook PMI reporting test with larger Tx ports |
Huawei, HiSilicon |
R4-2007203 |
Discussion on subband for Type I codebook PMI reporting test with larger Tx ports |
Huawei, HiSilicon |
R4-2007924 |
Addition of High spatial correlation matrices for 2D antenna arrays |
Ericsson |
R4-2007925 |
Addition of Rel-16 PMI FRC |
Ericsson |
R4-2007926 |
Addition of Rel-16 SP type I PMI tests |
Ericsson |
R4-2007927 |
Simulation results for CSI PMI SP type I test cases |
Ericsson |
R4-2007928 |
Summary of simulation results of NR UE CSI PMI with 16, and 32Tx antennas |
Ericsson |
R4-2007934 |
Evaluation on test setup for Rel-15 Type II codebook |
Ericsson |
R4-2007935 |
Simulation results for Rel-15 Type II codebook |
Ericsson |
R4-2008843 |
Addition of High spatial correlation matrices for 2D antenna arrays |
Ericsson |
R4-2008844 |
Addition of Rel-16 PMI FRC |
Ericsson |
R4-2008845 |
Addition of Rel-16 SP type I PMI tests |
Ericsson |
6.18.1.3 |
LTE-NR co-existence for TDD [NR_perf_enh-Perf] |
|
R4-2006532 |
CR to TS 38.101-4: CR on TDD LTE-NR coexistence requirements finalization |
Intel Corporation |
6.18.1.4 |
FR1 CA and EN-DC power imbalance requirements [NR_perf_enh-Perf] |
|
R4-2006039 |
FR1 CA PDSCH demodulation requirement with power imbalance |
China Telecom |
R4-2006533 |
Discussion on FR1 CA and EN-DC power imbalance requirements |
Intel Corporation |
R4-2006809 |
Discussion on FR1 CA and EN-DC power imbalance requirements |
CMCC |
R4-2007140 |
Views on power imbalance requirement |
NTT DOCOMO, INC. |
R4-2007224 |
Discussion on UE power imbalance requirements for FR1 CA and EN-DC |
Huawei, HiSilicon |
R4-2007882 |
Views on Power Imbalance Tests |
Qualcomm Incorporated |
6.18.1.5 |
NR CA CQI reporting requirements [NR_perf_enh-Perf] |
|
R4-2006040 |
On NR CA CQI reporting requirements |
China Telecom |
R4-2007142 |
Views on UE demodulation requirements for CA CQI |
NTT DOCOMO, INC. |
R4-2007225 |
Discussion on CA CQI reporting requirements |
Huawei, HiSilicon |
R4-2008113 |
Views on CA CQI Reporting Tests |
Qualcomm Incorporated |
6.18.2.1 |
30% TP test point [NR_perf_enh-Perf] |
|
R4-2006057 |
On NR Rel-16 performance requirement enhancement BS demodulation 30% TP test point |
Nokia, Nokia Shanghai Bell |
R4-2006250 |
Summary of ideal and impairment results for NR PUSCH with 30% throughput test point |
CATT |
R4-2006251 |
CR for TS 38.104: Introduce PUSCH performance requirements at 30% throughput test point |
CATT |
R4-2006252 |
CR for TS 38.141-1: Introduce PUSCH performance requirements at 30% throughput test point |
CATT |
R4-2006253 |
CR for TS 38.141-2: Introduce PUSCH performance requirements at 30% throughput test point |
CATT |
R4-2008850 |
CR for TS 38.104: Introduce PUSCH performance requirements at 30% throughput test point |
CATT |
R4-2008851 |
CR for TS 38.141-1: Introduce PUSCH performance requirements at 30% throughput test point |
CATT |
R4-2008852 |
CR for TS 38.141-2: Introduce PUSCH performance requirements at 30% throughput test point |
CATT |
6.18.2.2 |
Additional FR2 requirements [NR_perf_enh-Perf] |
|
R4-2006058 |
CR for 38.104: Performance requirements for FR2 PUSCH 2T2R 16QAM |
Nokia, Nokia Shanghai Bell |
R4-2006059 |
CR for 38.141-2: Radiated test requirements for FR2 PUSCH 2T2R 16QAM |
Nokia, Nokia Shanghai Bell |
6.19 |
Over the air (OTA) base station (BS) testing TR [OTA_BS_testing-Perf] |
|
R4-2008700 |
Email discussion summary for [95e][311] OTA_BS_testing |
Moderator (Huawei) |
R4-2009045 |
Email discussion summary for [95e][311] OTA_BS_testing |
Moderator (Huawei) |
6.19.1 |
General [OTA_BS_testing-Perf] |
|
R4-2007566 |
TP to TR 37.941: Improvement of technical background information in Clause 6 |
Ericsson, Rohde & Schwarz |
R4-2008137 |
TP to TR 37.941: editorial cleanup |
Huawei |
R4-2008853 |
TP to TR 37.941: editorial cleanup |
Huawei |
R4-2008854 |
TP to TR 37.941: Improvement of technical background information in Clause 6 |
Ericsson, Rohde & Schwarz |
R4-2009064 |
Draft TR 37.941 v0.3.0 |
Huawei |
6.19.2 |
OTA calibration and test method procedures [OTA_BS_testing-Perf] |
|
R4-2007568 |
TP to TR 37.941: Improvement of the Clause 6.3.3 |
Ericsson |
R4-2008855 |
TP to TR 37.941: Improvement of the Clause 6.3.3 |
Ericsson |
6.19.5 |
MU / TT values: derivation and tables [OTA_BS_testing-Perf] |
|
R4-2007595 |
TP to 37.941: MU tables for additional Tx test cases for PWS |
ROHDE & SCHWARZ |
R4-2007910 |
TX directional FR2 MU budget spreadsheet |
Huawei |
R4-2007911 |
TP to TR 37.941 FR2 TX directional |
Huawei |
R4-2007912 |
RX directional FR2 MU budget spreadsheet |
Huawei |
R4-2007913 |
TP to TR 37.941 FR2 RX directional |
Huawei |
R4-2007914 |
TP to TR 37.941 MU budget procedure update |
Huawei |
R4-2007915 |
TP to TR 37.941 EIRP MU budget procedure update |
Huawei |
R4-2008856 |
TP to TR 37.941 MU budget procedure update |
Huawei |
R4-2008857 |
TP to TR 37.941 EIRP MU budget procedure update |
Huawei |
R4-2008858 |
TP to 37.941: MU tables for additional Tx test cases for PWS |
ROHDE & SCHWARZ |
R4-2008859 |
TX directional FR2 MU budget spreadsheet |
Huawei |
R4-2008860 |
RX directional FR2 MU budget spreadsheet |
Huawei |
6.19.7 |
Others [OTA_BS_testing-Perf] |
|
R4-2007451 |
CR to TR 37.842: internal TR references corrections and content redundancy removal (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
R4-2007452 |
CR to TR 37.843: internal TR references corrections and content redundancy removal (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
R4-2007453 |
CR to TR 38.817-02: internal TR references corrections and content redundancy removal (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
R4-2007454 |
CR to TS 37.145-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
R4-2007455 |
CR to TS 37.145-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-16 |
Huawei |
R4-2007456 |
CR to TS 38.141-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
R4-2007457 |
CR to TS 38.141-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-16 |
Huawei |
R4-2007458 |
CR to TS 37.114: internal TR reference corrections, Rel-15 |
Huawei |
R4-2008005 |
TP to TR 37.941 on editorial corrections for PWS references |
ROHDE & SCHWARZ |
R4-2008861 |
CR to TR 37.842: internal TR references corrections and content redundancy removal (wrt. TR 37.941 for OTA BS testing), Rel-13 |
Huawei |
R4-2008862 |
CR to TR 37.843: internal TR references corrections and content redundancy removal (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
R4-2008863 |
CR to TR 38.817-02: internal TR references corrections and content redundancy removal (wrt. TR 37.941 for OTA BS testing), Rel-15 |
Huawei |
6.20.1 |
RRM core requirements (38.133) [NR_2step_RACH-Core] |
|
R4-2006601 |
CR to TS 38.133: introducing 2-step RACH core requirements |
Nokia, Nokia Shanghai Bell, ZTE |
R4-2006605 |
On RRM core requirements for 2-step RA type |
Nokia, Nokia Shanghai Bell |
R4-2007293 |
Discussion on RRM Requirements for 2-step RACH |
NEC |
R4-2007491 |
RRM core requirements for 2-step RACH |
Qualcomm |
R4-2007652 |
Remaining open issues on RRM requirements for 2-step RACH |
ZTE |
R4-2007653 |
CR to 38.133 on UE transmit timing requirements for 2-step RACH |
ZTE |
R4-2007869 |
discussion on 2-step RA requirements |
Huawei, HiSilicon |
R4-2008000 |
On defining 2-step RA and 4-step RA in exisitng RRM requirements |
Ericsson |
R4-2008001 |
Applicability of 2-step RA and 4-step RA in RRM requirements in 38.133 |
Ericsson |
R4-2008002 |
Applicability of 2-step RA and 4-step RA in RRM requirements in 36.133 |
Ericsson |
R4-2008517 |
Email discussion summary for [95e][228] NR_2step_RACH_RRM |
Moderator (ZTE) |
R4-2008636 |
WF on RRM requirements for 2-step RACH |
ZTE |
R4-2008637 |
CR to TS 38.133: introducing 2-step RACH core requirements |
Nokia, Nokia Shanghai Bell, ZTE |
R4-2008638 |
CR to 38.133 on UE transmit timing requirements for 2-step RACH |
ZTE |
R4-2008639 |
Applicability of 2-step RA and 4-step RA in RRM requirements in 38.133 |
Ericsson |
R4-2008640 |
Applicability of 2-step RA and 4-step RA in RRM requirements in 36.133 |
Ericsson |
R4-2009090 |
Email discussion summary for [95e][228] NR_2step_RACH_RRM |
Moderator (ZTE) |
6.20.2 |
BS Demodulation requirements (38.104/38.141-1/38.141-2) [NR_2step_RACH-Perf] |
|
R4-2006540 |
Views on BS demodulation requirements for NR 2-Step RACH |
Intel Corporation |
R4-2006604 |
On 2-step RACH BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2006661 |
Initial simulation results on BS demodulation for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2006662 |
Further discussion on BS demodulation performance requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2007238 |
Discussion on NR 2-step RACH performance requirements |
Huawei, HiSilicon |
R4-2007365 |
2-step RACH parameter proposals |
Ericsson |
R4-2008714 |
Email discussion summary for [95e][325] NR_2step_RACH_Demod |
Moderator (ZTE) |
R4-2008864 |
WF on BS demodulation requirements for 2-step RACH |
ZTE |
R4-2009046 |
Email discussion summary for [95e][325] NR_2step_RACH_Demod |
Moderator (ZTE) |
6.21.2 |
UE RF [WI code or TEI16] |
|
R4-2006242 |
CR for TS38.101-3, Aligned IE RF-Parameters name of maxUplinkDutyCycle with RAN2 |
CATT |
R4-2006347 |
CR Coexistence cleanup for 38101-1 Rel16 |
Apple Inc. |
R4-2006482 |
Usage of n77 in US C-band REL-15 |
Nokia |
R4-2006483 |
Usage of n77 in US C-band REL-16 |
Nokia |
R4-2006484 |
C-band co-existence aspects. |
Nokia |
R4-2006497 |
Proposed response to RAN2 LS on asymmetric channel bandwidths |
Nokia |
R4-2006617 |
Update 4Rx Requirement for Band n30 |
AT&T, Nokia, Ericsson |
R4-2006624 |
Band n77 usage in the US |
Apple |
R4-2006744 |
CR to 38.101-2 to correct Link and Meas Angles |
Keysight Technologies UK Ltd |
R4-2006759 |
CR to 38.101-1: Introduce an operating band list and NR bands to UL MIMO |
Verizon UK Ltd |
R4-2006938 |
CR on blocking requirements for n91 n92 n93 and n94 |
Huawei, HiSilicon |
R4-2006947 |
Endorsed CR on default AMPR signaling for n91 n92 n93 and n94 |
Huawei, HiSilicon |
R4-2007334 |
Reply LS on asymmetric channel bandwidths |
Huawei, HiSilicon |
R4-2008086 |
CR on introduce delta-MPR for inter-band CA in band n28 and review value with brackets |
Huawei, HiSilicon |
R4-2008114 |
CR for Band 53 NS_45 requirement and OOB blocking |
Qualcomm Incorporated |
R4-2008118 |
UE perspective of Band n77 for US C-band |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple |
R4-2008119 |
Addition of UE coexistence between US bands and NR Band n77 |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple, Ericsson |
R4-2008120 |
Addition of mutual UE coexistence between US bands and NR Band n77 |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple, Ericsson |
R4-2008121 |
Addition of UE coexistence between US DC combinations and NR Band n77 |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple, Ericsson |
R4-2008176 |
CR for power class fallback enhancement |
Huawei, HiSilicon |
R4-2008225 |
CR for TS 38.101-1 UE co-existence correction (R16) |
Huawei, HiSilicon |
R4-2008227 |
CR for 38.101-1 RFC corrections (R16) |
Huawei, HiSilicon |
R4-2008267 |
Further discussion on linear method for power class fall back optimization |
vivo |
R4-2008316 |
Email discussion summary for [95e][126] NR_R16_Maintenance |
Moderator (Dish Network) |
R4-2008893 |
Reply LS on asymmetric channel bandwidths |
RAN4 |
R4-2008894 |
CR to 38.101-1: Introduce an operating band list and NR bands to UL MIMO |
Verizon UK Ltd |
R4-2008895 |
WF on NR bands to UL MIMO |
Samsung |
R4-2008896 |
CR on blocking requirements for n91 n92 n93 and n94 |
Huawei, HiSilicon |
R4-2008897 |
Addition of UE coexistence between US bands and NR Band n77 |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple, Ericsson |
R4-2008898 |
Addition of mutual UE coexistence between US bands and NR Band n77 |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple, Ericsson |
R4-2008899 |
Addition of UE coexistence between US DC combinations and NR Band n77 |
Qualcomm Incorporated, Verizon, T-Mobile USA, AT&T, Apple, Ericsson |
R4-2008956 |
Email discussion summary for [95e][126] NR_R16_Maintenance |
Moderator (Dish Network) |
R4-2009162 |
CR to 38.101-1: Introduce an operating band list and NR bands to UL MIMO |
Verizon UK Ltd |
6.21.3 |
RRM [WI code or TEI16] |
|
R4-2006184 |
CR on measurement gap applicability in TS38.133 for R16 |
Apple |
R4-2006217 |
Rapportuer CR for TS38.133 |
Apple |
R4-2006616 |
On potential enhancement for TCI switching |
Apple |
R4-2006882 |
Reply LS on NeedForGap capability |
MediaTek inc. |
R4-2006883 |
Discussion on NeedForGap capability |
MediaTek inc. |
R4-2007657 |
CR to 38.133 on intra frequency measurements without gaps |
ZTE |
R4-2008662 |
Rapportuer CR for TS38.133 |
Apple |
R4-2008997 |
Reply LS on NeedForGap capability |
RAN4 |
R4-2009130 |
CR to 38.133 on intra frequency measurements without gaps |
ZTE |
R4-2009270 |
Rapportuer CR for TS38.133 |
Apple |
7 |
UE feature list |
|
R4-2006348 |
Further views on NR UE feature list for FR1 |
Apple Inc. |
R4-2006349 |
Further views on NR UE feature list for FR2 |
Apple Inc. |
R4-2006901 |
RAN4 UE features list for Rel-16 |
NTT DOCOMO, INC. |
R4-2007637 |
Views on Rel-16 NR/LTE UE feature list |
Intel Corporation |
R4-2008251 |
On Rel-16 feature list |
Huawei, HiSilicon |
R4-2008317 |
Email discussion summary for [95e][127] R16_UE_ feature |
Moderator (NTT DOCOMO) |
R4-2008900 |
RAN4 UE features list for Rel-16 |
NTT DOCOMO, INC. |
R4-2008901 |
LS on Rel-16 RAN4 UE features lists for NR and LTE |
NTT DOCOMO, INC |
R4-2008957 |
Email discussion summary for [95e][127] R16_UE_ feature |
Moderator (NTT DOCOMO) |
R4-2009173 |
LS on Rel-16 RAN4 UE features lists for NR and LTE |
RAN4 |
R4-2009174 |
RAN4 UE features list for Rel-16 |
NTT DOCOMO, INC. |
8 |
Rel-16 spectrum related Work Items for NR |
|
R4-2007636 |
CR Rel-16 for editorial corrections TS 38.101-3 |
Ericsson |
R4-2008318 |
Email discussion summary for [95e][128] NR_Baskets_Part_1 |
Moderator (Nokia) |
8.1.1 |
Rapporteur Input (WID/TR/CR) [NR_CA_R16_intra-Core /Perf] |
|
R4-2006045 |
TR 38.716-01-01 v0.12.0 Rel-16 NR Intra-band |
Ericsson |
R4-2007597 |
Revised WID NR Intra-band Rel-16 |
Ericsson |
R4-2007605 |
CR introduction completed band combinations 38.716-01-01 - |
Ericsson |
R4-2007606 |
CR introduction completed band combinations 38.716-01-01 - |
Ericsson |
8.1.2 |
UE RF for FR1 [NR_CA_R16_intra-Core] |
|
R4-2006066 |
Corrections to CA n48 |
Dish Network |
R4-2006425 |
TP for TR 38.716-01-01 CA_n77(2A)_UL_n77(2A) |
Samsung, KDDI |
R4-2006426 |
TP for TR 38.716-01-01 CA_n78(2A)_UL_n78(2A) |
Samsung, KDDI |
R4-2006492 |
CA_n48B A-MPR |
Nokia |
R4-2008038 |
DraftCR for TS 38.101-1 intra-band UL contiguous CA combinations CA_n79C |
Huawei, HiSilicon, CMCC |
8.1.3 |
UE RF for FR2 [NR_CA_R16_intra-Core] |
|
R4-2006704 |
CR to 38.101-2: Introduce mmWave intra-band uplink CA configurations |
Verizon UK Ltd |
R4-2006708 |
CR to 38.101-2: Conrrection of aggregated bandwidth for CA_n261(2A-G) in Table 5.5A.2-2 |
Verizon UK Ltd |
R4-2006830 |
CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications |
MediaTek Inc. |
R4-2008381 |
CR to 38.101-2: Introduce mmWave intra-band uplink CA configurations |
Verizon UK Ltd |
8.2 |
NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) [NR_CADC_R16_2BDL_xBUL] |
|
R4-2008319 |
Email discussion summary for [95e][129] NR_Baskets_Part_2 |
Moderator (Nokia) |
8.2.1 |
Rapporteur Input (WID/TR/CR) [NR_CADC_R16_2BDL_xBUL-Core/Perf] |
|
R4-2006872 |
TR 38.716-02-00 v120 |
ZTE Wistron Telecom AB |
R4-2007019 |
Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
R4-2007020 |
CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into Rel16 TS 38.101-1 |
ZTE Corporation |
R4-2007021 |
CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into Rel16 TS 38.101-3 |
ZTE Corporation |
8.2.2 |
NR inter band CA without any FR2 band(s) [NR_CADC_R16_2BDL_xBUL-Core] |
|
R4-2006067 |
Corrections to n29-n66 CA combinations |
Dish Network |
R4-2006298 |
Draft CR on introducing CA_n41C-n79A |
CATT |
R4-2006393 |
darft CR for 38.101-1 to introduce UL CA configuration for inter-band NR CA |
Samsung, KDDI |
R4-2006606 |
TP to TR 38.716-02-00 for CA_n5-n66 with dual UL |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2006690 |
TP for TR 38.716-02-00: CA_n2-n77 |
Verizon UK Ltd |
R4-2006693 |
TP for TR 38.716-02-00: CA_n5-n77 |
Verizon UK Ltd |
R4-2006694 |
TP for TR 38.716-02-00: CA_n66-n77 |
Verizon UK Ltd |
R4-2006748 |
CR to add simultaneous RXTX capability for CA_n41-n79 |
CMCC, ZTE |
R4-2006937 |
TP to TR 38.716-02-00 CA_n78(2A)-n92A |
Huawei, HiSilicon |
R4-2007009 |
Draft CR to TS38.101-1: CA_n28A-n75A |
ZTE Corporation |
R4-2007010 |
Draft CR to TS 38.101-1: Updated the MSD values for NR CA n3-n41 |
ZTE Corporation |
R4-2007011 |
TP for TR 38.716-02-00:CA_n38A-n78A |
ZTE Corporation, Bell Mobility, Telus |
R4-2007326 |
TP to TR 38.716-02-00 for CA_n38-n78 |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007624 |
TP for TR 38.716-02-00 to include CA_n5-n7 |
Ericsson, Telstra |
R4-2007625 |
TP for TR 38.716-02-00 to include CA_n3-n7 |
Ericsson, Telstra, BT plc |
R4-2007626 |
draft Rel-16 CR to 38.101-1 to add CA_n1A-n7B, CA_n7B-n28A |
Ericsson, Telstra |
R4-2008036 |
Draft CR for 38.101-1 to add configuration CA_n75A-n78(2A) and simplify the REFSENS for inter band CA with SDL |
Huawei, HiSilicon,Etisalat |
R4-2008089 |
CR for 38.101-1: to add some missing sub-clause title for NR inter-band CA |
Huawei, HiSilicon |
R4-2008349 |
Draft CR on introducing CA_n41C-n79A |
CATT |
R4-2008350 |
darft CR for 38.101-1 to introduce UL CA configuration for inter-band NR CA |
Samsung, KDDI |
R4-2008351 |
TP to TR 38.716-02-00 for CA_n5-n66 with dual UL |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2008352 |
TP for TR 38.716-02-00: CA_n2-n77 |
Verizon UK Ltd |
R4-2008353 |
TP for TR 38.716-02-00: CA_n5-n77 |
Verizon UK Ltd |
R4-2008354 |
TP for TR 38.716-02-00: CA_n66-n77 |
Verizon UK Ltd |
R4-2008355 |
CR to add simultaneous RXTX capability for CA_n41-n79 |
CMCC, ZTE |
R4-2008356 |
TP to TR 38.716-02-00 CA_n78(2A)-n92A |
Huawei, HiSilicon |
R4-2008357 |
TP for TR 38.716-02-00:CA_n38A-n78A |
ZTE Corporation, Bell Mobility, Telus |
R4-2008358 |
TP for TR 38.716-02-00 to include CA_n3-n7 |
Ericsson, Telstra, BT plc |
R4-2008359 |
Draft CR for 38.101-1 to add configuration CA_n75A-n78(2A) and simplify the REFSENS for inter band CA with SDL |
Huawei, HiSilicon,Etisalat |
R4-2008360 |
CR for 38.101-1: to add some missing sub-clause title for NR inter-band CA |
Huawei, HiSilicon |
R4-2008361 |
CR for 38.101-1: to add some missing sub-clause title for NR inter-band CA |
Huawei, HiSilicon |
8.2.3 |
NR inter band CA with at least one FR2 band [NR_CADC_R16_2BDL_xBUL-Core] |
|
R4-2006622 |
Draft CR for 38.101-3: Support of n78C in the DC_n78-n257 and CA_n78-n257 |
SK Telecom |
R4-2006673 |
Draft CR for TS 38.101-3: Support of DC_n3-n257 and DC_n28-n257 |
SoftBank Corp. |
R4-2006697 |
TP for TR 38.716-02-00: CA_n77-n261 |
Verizon UK Ltd |
R4-2008362 |
Draft CR for TS 38.101-3: Support of DC_n3-n257 and DC_n28-n257 |
SoftBank Corp. |
R4-2008363 |
TP for TR 38.716-02-00: CA_n77-n261 |
Verizon UK Ltd |
8.3 |
EN-DC of 1 LTE band and 1 NR band [DC_R16_1BLTE_1BNR_2DL2UL] |
|
R4-2008135 |
DC_12_n71 Single Uplink Operation |
Skyworks Solutions Inc. |
8.3.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_1BLTE_1BNR_2DL2UL-Core/Perf] |
|
R4-2006845 |
TR 37.716-11-11 v.1.3.0 Rel.16 1 LTE band + 1 NR band EN-DC |
CHTTL |
R4-2006890 |
Big CR on introduction of completed EN-DC of 1 band LTE and 1 band NR |
CHTTL |
R4-2006895 |
Revised WID on EN-DC for 2 bands DL with 2 bands UL (1 LTE band + 1 NR band) |
CHTTL |
8.3.2 |
EN-DC without FR2 band [DC_R16_1BLTE_1BNR_2DL2UL-Core] |
|
R4-2006142 |
TP for TR 37.716-11-11: DC_48A-48A_n71A and DC_48A-48A-48A_n71A |
CableLabs, Comcast |
R4-2006456 |
CR for TS 38.101-3: Adding missing MSD due to UL harmonic for DC_28_n50 |
MediaTek Inc. |
R4-2006618 |
Draft CR for 38.101-3: Support of n78C in DC_5_n78, and DC_7_n78 |
SK Telecom |
R4-2006686 |
TP update for TR 37.716-11-11: DC_42_n28 |
SoftBank Corp. |
R4-2006687 |
TP update for TR 37.716-11-11: DC_11_n28 |
SoftBank Corp., LG Electronics Inc. |
R4-2006699 |
TP for TR 37.716-11-11: DC_13_n2 |
Verizon UK Ltd |
R4-2006877 |
Draft CR to 38.101-3 on the correction of DC_48D_n48A |
Google Inc. |
R4-2006926 |
TP for TR 37.716-11-11: some corrections for TR 37.716-11-11 |
CHTTL |
R4-2006952 |
Correction to EN-DC coexistence requirements |
Rohde & Schwarz |
R4-2007012 |
Draft CR to TS 38.101-3: Editorial corrections on the MSD values due to cross bands isolation for DC_1-n3 and DC_3-n41 |
ZTE Corporation |
R4-2007170 |
TP for 37.716-11-11 to introduce DC_5_n5 |
Nokia, Verizon |
R4-2007611 |
TP for TR 37.716-11-11 to include 2_n2 |
Ericsson, AT&T, Nokia, Verizon |
R4-2007612 |
TP for TR 37.716-11-11 to include 14_n66 |
Ericsson, AT&T |
R4-2007613 |
TP for TR 37.716-11-11 to include 14_n2 |
Ericsson, AT&T |
R4-2007623 |
TP for TR 37.716-11-11 to include DC_12_n71 |
Ericsson, US Cellular |
R4-2008016 |
TP for TR 37.716-11-11: DC_7A_n20A |
Huawei, HiSilicon |
R4-2008341 |
TP update for TR 37.716-11-11: DC_11_n28 |
SoftBank Corp., LG Electronics Inc. |
R4-2008342 |
TP for 37.716-11-11 to introduce DC_5_n5 |
Nokia, Verizon |
R4-2008343 |
TP for TR 37.716-11-11 to include 2_n2 |
Ericsson, AT&T, Nokia, Verizon |
R4-2008344 |
TP for TR 37.716-11-11 to include DC_12_n71 |
Ericsson, US Cellular |
R4-2008376 |
TP for TR 37.716-11-11 to correct DC_13_n5 |
Ericsson |
8.4.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_2BLTE_1BNR_3DL2UL-Core/Perf] |
|
R4-2007337 |
TR 37.716-21-11 v0.11.0 |
Huawei, HiSilicon |
R4-2007338 |
Revised WID: Dual Connectivity (EN-DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
R4-2007339 |
CR on introduction of completed EN-DC of 2 bands LTE and 1 band NR from RAN4#94bis-e and RAN4#95-e into TS 38.101-3 |
Huawei, HiSilicon |
8.4.2 |
EN-DC without FR2 band [DC_R16_2BLTE_1BNR_3DL2UL-Core] |
|
R4-2006395 |
TP for TR 37.716-21-11 DC_3-41_n28 update |
Samsung, KDDI, LGE |
R4-2006498 |
TP for TR 37.716-21-11: DC_2-29_n66 and DC_2-2-29_n66 |
Nokia |
R4-2006499 |
TP for TR 37.716-21-11: DC_29-66_n2 and DC_29-66-66_n2 |
Nokia |
R4-2006619 |
Draft CR for 38.101-3: Support of n78C in DC_1-5_n78, DC_1-7_n78, DC_3-5_n78, DC_3-7_n78, and DC_5-7_n78 |
SK Telecom |
R4-2006672 |
Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-42_n77, DC_3-42_n77 and DC_8-42_n77 |
SoftBank Corp. |
R4-2006679 |
TP for TR 37.716-21-11: EN-DC_1-42_n28 |
SoftBank Corp. |
R4-2006681 |
TP for TR 37.716-21-11: EN-DC_3-42_n28 |
SoftBank Corp. |
R4-2006682 |
TP for TR 37.716-21-11: EN-DC_8-42_n28 |
SoftBank Corp. |
R4-2006689 |
TP update for TR 37.716-21-11: DC_1-11_n3 |
SoftBank Corp., LG Electronics Inc. |
R4-2006934 |
TP to TR 37.716-21-11 DC_3C-20A_n41A |
Huawei, HiSilicon |
R4-2007614 |
TP for TR 37.716-21-11 to include 2-14_n66 |
Ericsson, AT&T |
R4-2007615 |
TP for TR 37.716-21-11 to include 2-14_n2 |
Ericsson, AT&T |
R4-2007616 |
TP for TR 37.716-21-11 to include 14-66_n2 |
Ericsson, AT&T |
R4-2007617 |
TP for TR 37.716-21-11 to include 46-66_n5 |
Ericsson, AT&T |
R4-2007618 |
TP for TR 37.716-21-11 to include 14-66_n66 |
Ericsson, AT&T |
R4-2008017 |
TP for TR 37.716-21-11: DC_3A-(n)41AA\DC_3A-(n)41CA\DC_3A-(n)41DA |
Huawei, HiSilicon,Etisalat |
R4-2008018 |
TP for TR 37.716-21-11: DC_3A-41A_n41A\DC_3A-41C_n41A\DC_3A-41D_n41A |
Huawei, HiSilicon |
R4-2008340 |
TP for TR 37.716-21-11: EN-DC_8-42_n28 |
SoftBank Corp. |
R4-2008345 |
TP for TR 37.716-21-11: DC_3A-(n)41AA\DC_3A-(n)41CA\DC_3A-(n)41DA |
Huawei, HiSilicon,Etisalat |
R4-2008346 |
TP for TR 37.716-21-11: DC_3A-41A_n41A\DC_3A-41C_n41A\DC_3A-41D_n41A |
Huawei, HiSilicon |
R4-2008378 |
TP for TR 37.716-21-11 to add MSD for DC_2A-5A_n71A |
Ericsson |
8.4.3 |
EN-DC with FR2 band [DC_R16_2BLTE_1BNR_3DL2UL-Core] |
|
R4-2006394 |
Draft CR for 38.101-3 to introduce new UL EN-DC configuration for DC_1-11_n257 |
Samsung, KDDI |
R4-2006396 |
TP for TR 37.716-21-11 DC_11-18_n257 |
Samsung, KDDI |
R4-2006397 |
TP for TR 37.716-21-11 DC_18-41_n257 |
Samsung, KDDI |
R4-2007619 |
TP for TR 37.716-21-11 to include 2-46_n260 |
Ericsson, AT&T |
R4-2007620 |
TP for TR 37.716-21-11 to include 46-66_n260 |
Ericsson, AT&T |
R4-2008335 |
TP for TR 37.716-21-11 DC_11-18_n257 |
Samsung, KDDI |
8.5.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_3BLTE_1BNR_4DL2UL-Core/Perf] |
|
R4-2006046 |
TR 37.716-31-11 v0.12.0 Rel-16 DC combinations LTE 3DL and one NR band |
Ericsson |
R4-2007598 |
Revised WID LTE 3DL and one NR band Rel-16 |
Ericsson |
R4-2007607 |
CR introduction completed band combinations 37.716-31-11 - |
Ericsson |
8.5.2 |
EN-DC without FR2 band [DC_R16_3BLTE_1BNR_4DL2UL-Core] |
|
R4-2006418 |
TP for TR 37.716-31-11 DC_1-11-18_n77 |
Samsung, KDDI |
R4-2006419 |
TP for TR 37.716-31-11 DC_1-11-18_n78 |
Samsung, KDDI |
R4-2006421 |
TP for TR 37.716-31-11 DC_1-18-41_n3 |
Samsung, KDDI |
R4-2006422 |
TP for TR 37.716-31-11 DC_1-18-41_n77 |
Samsung, KDDI |
R4-2006423 |
TP for TR 37.716-31-11 DC_1-18-41_n78 |
Samsung, KDDI |
R4-2006500 |
TP for TR 37.716-31-11:DC_2A-29A-66A_n66A |
Nokia |
R4-2006501 |
TP for TR 37.716-31-11:DC_29A-30A-66A_n66A |
Nokia |
R4-2006502 |
TP for TR 37.716-31-11:DC_29A-30A-66A_n2A |
Nokia |
R4-2006503 |
TP for TR 37.716-31-11:DC_2A-29A-30A_n2A |
Nokia |
R4-2006504 |
TP for TR 37.716-31-11:DC_2A-29A-66A_n2A |
Nokia |
R4-2006505 |
TP for TR 37.716-31-11:DC_2A-30A-66A_n2A |
Nokia |
R4-2006506 |
TP for TR 37.716-31-11:DC_29A-30A-66A-66A_n2A |
Nokia |
R4-2006507 |
TP for TR 37.716-31-11:DC_2A-29A-66A-66A_n2A |
Nokia |
R4-2006508 |
TP for TR 37.716-31-11:DC_2A-30A-66A-66A_n2A |
Nokia |
R4-2006620 |
Draft CR for 38.101-3: Support of n78C in DC_1-3-5_n78, DC_1-3-7_n78, DC_1-5-7_n78, and DC_3-5-7_n78 |
SK Telecom |
R4-2006670 |
Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-3-8_n77 and DC_1-8-42_n77 |
SoftBank Corp. |
R4-2006676 |
TP for TR 37.716-31-11: EN-DC_1-3-8_n28 |
SoftBank Corp. |
R4-2006831 |
TP for TR 37.716-31-11: UE requirements for DC_3A-7A-8A_n77A |
CHTTL |
R4-2006935 |
TP to TR 37.716-31-11 DC_1A-3C-20A_n41A |
Huawei, HiSilicon |
R4-2007171 |
TP for 37.716-31-11 to introduce DC_2-5-66_n2 |
Nokia, Verizon |
R4-2007172 |
TP for 37.716-31-11 to introduce DC_2-5-66_n5 |
Nokia, Verizon |
R4-2007173 |
TP for 37.716-31-11 to introduce DC_2-13-66_n2 |
Nokia, Verizon |
R4-2007621 |
TP for TR 37.716-31-11 to include 2-14-66_n66 |
Ericsson, AT&T |
R4-2007622 |
TP for TR 37.716-31-11 to include 2-14-66_n2 |
Ericsson, AT&T |
R4-2007634 |
draft Rel-16 CR to 38.101-3 to add DC_3C-7C-20A_n1A |
Ericsson, BT plc |
R4-2008019 |
TP for TR 37.716-31-11: DC_1A-3A-7A_n8A |
Huawei, HiSilicon |
R4-2008020 |
TP for TR 37.716-31-11: DC_1A-3A-20A_n8A |
Huawei, HiSilicon |
R4-2008021 |
TP for TR 37.716-31-11: DC_1A-7A-20A_n8A |
Huawei, HiSilicon |
R4-2008022 |
TP for TR 37.716-31-11: DC_3A-7A-20A_n8A |
Huawei, HiSilicon |
R4-2008023 |
TP for TR 37.716-31-11: DC_1A-7A-8A_n3A |
Huawei, HiSilicon |
R4-2008024 |
TP for TR 37.716-31-11: DC_1A-20A_(n)38AA |
Huawei, HiSilicon |
R4-2008025 |
TP for TR 37.716-31-11: DC_1A-3A-32A_n78A\DC_1A-3A-32A_n78(2A) |
Huawei, HiSilicon, CKH IOD UK |
R4-2008336 |
TP for TR 37.716-31-11 DC_1-11-18_n77 |
Samsung, KDDI |
R4-2008337 |
TP for TR 37.716-31-11 DC_1-11-18_n78 |
Samsung, KDDI |
R4-2008338 |
TP for TR 37.716-31-11 DC_1-18-41_n3 |
Samsung, KDDI |
R4-2008339 |
TP for TR 37.716-31-11 DC_1-18-41_n77 |
Samsung, KDDI |
R4-2008347 |
TP for TR 37.716-31-11: DC_1A-3A-7A_n8A |
Huawei, HiSilicon |
R4-2008348 |
TP for TR 37.716-31-11: DC_1A-7A-8A_n3A |
Huawei, HiSilicon |
8.5.3 |
EN-DC with FR2 band [DC_R16_3BLTE_1BNR_4DL2UL-Core] |
|
R4-2006420 |
TP for TR 37.716-31-11 DC_1-11-18_n257 |
Samsung, KDDI |
R4-2006424 |
TP for TR 37.716-31-11 DC_1-18-41_n257 |
Samsung, KDDI |
8.6.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_4BLTE_1BNR_5DL2UL-Core/Perf] |
|
R4-2007166 |
Revised Rel-16 WID on Dual Connectivity (EN-DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL) |
Nokia, Nokia Shanghai Bell |
R4-2007167 |
CR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 |
Nokia, Nokia Shanghai Bell |
R4-2007168 |
draftTR 37.716-41-11 v0.10.0 |
Nokia, Nokia Shanghai Bell |
8.6.2 |
EN-DC without FR2 band [DC_R16_4BLTE_1BNR_5DL2UL-Core] |
|
R4-2006509 |
TP for TR 37.716-41-11:DC_2A-29A-30A-66A_n2A |
Nokia |
R4-2006621 |
Draft CR for 38.101-3: Support of n78C in DC_1-3-5-7_n78 |
SK Telecom |
R4-2008026 |
TP for TR 37.716-41-11: DC_1A-3A-7A-20A_n8A |
Huawei, HiSilicon |
8.7.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_xBLTE_2BNR_yDL2UL-Core/Per] |
|
R4-2006726 |
TR 37.716-21-21 v1.0.0 update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 |
LG Electronics France |
R4-2006727 |
Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) EN DC in Rel-16 |
LG Electronics France |
R4-2006728 |
Introducing CR on new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 |
LG Electronics France |
8.7.2 |
EN-DC including NR inter CA without FR2 band [DC_R16_xBLTE_2BNR_yDL2UL-Core] |
|
R4-2006410 |
TP for TR 37.716-21-21 DC_18_n3-n77 update |
Samsung, KDDI, LGE |
R4-2006412 |
TP for TR 37.716-21-21 DC_41_n3-n77 update |
Samsung, KDDI, LGE |
R4-2006413 |
TP for TR 37.716-21-21 DC_41_n3-n78 update |
Samsung, KDDI, LGE |
R4-2006589 |
TP to TR 37.716-21-11: DC_20_n1-n7 |
Nokia, Nokia, Shanghai Bell, BT plc |
R4-2006590 |
TP to TR 37.716-21-11: DC_3-20_n1-n7 |
Nokia, Nokia, Shanghai Bell, BT plc |
R4-2006675 |
TP for TR 37.716-21-21: EN-DC_1-3_n28-n77 |
SoftBank Corp. |
R4-2006677 |
TP for TR 37.716-21-21: EN-DC_1-8_n3-n28 |
SoftBank Corp. |
R4-2006678 |
TP for TR 37.716-21-21: EN-DC_1-8_n28-n77 |
SoftBank Corp. |
R4-2006680 |
TP for TR 37.716-21-21: EN-DC_3-8_n28-n77 |
SoftBank Corp. |
R4-2006684 |
TP for TR 37.716-21-21: EN-DC_42_n28-n77 |
SoftBank Corp. |
R4-2006729 |
TP on summary of self-interference analysis for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-16 |
LG Electronics France |
R4-2006936 |
TP to TR 37.716-21-21 DC_20A_n78(2A)-n92A |
Huawei, HiSilicon |
R4-2007013 |
TP for TR37.716-21-21: DC_1A-3A-20A_n38A-n78A |
ZTE Corporation |
R4-2007014 |
TP for TR37.716-21-21_ DC_3A-20A_n38A-n78A |
ZTE Corporation |
R4-2007327 |
TP for TR 37.716-21-21: DC_2A_n38A-n78A |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007328 |
TP for TR 37.716-21-21: DC_66A_n38A-n78A |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007329 |
TP for TR 37.716-21-21: DC_2A-66A_n38A-n78A |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007330 |
TP for TR 37.716-21-21: DC_5_n7-n78 |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007331 |
TP for TR 37.716-21-21: DC_12_n7-n78 |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007332 |
TP for TR 37.716-21-21: DC_66_n7-n78 |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2007333 |
TP for TR 37.716-21-21: DC_2_n7-n78 |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2008027 |
TP for TR 37.716-21-21: DC_1A_n75A-n78A\DC_1A_n75A-n78(2A) |
Huawei, HiSilicon, CKH IOD UK |
R4-2008028 |
TP for TR 37.716-21-21: DC_3A_n75A-n78A\DC_3A_n75A-n78(2A) |
Huawei, HiSilicon, CKH IOD UK |
R4-2008029 |
TP for TR 37.716-21-21: DC_1A-3A_n41A-n78A |
Huawei, HiSilicon |
R4-2008030 |
TP for TR 37.716-21-21: DC_1A-20A_n41A-n78A |
Huawei, HiSilicon |
R4-2008031 |
TP for TR 37.716-21-21: DC_3A-20A_n41A-n78A |
Huawei, HiSilicon |
R4-2008032 |
TP for TR 37.716-21-21: DC_1A-7A_n3A-n78A |
Huawei, HiSilicon, Telefonica |
R4-2008033 |
TP for TR 37.716-21-21: DC_3A-20A_n7A-n28A/DC_3C-20A_n7A-n28A |
Huawei, HiSilicon, BT plc |
R4-2008034 |
TP for TR 37.716-21-21: DC_1A-3A-20A_n41A-n78A |
Huawei, HiSilicon |
R4-2008035 |
TP for TR 37.716-21-21: DC_(n)41AA-n78A\DC_(n)41CA-n78A\DC_(n)41DA-n78A |
Huawei, HiSilicon,Etisalat |
R4-2008364 |
TP for TR 37.716-21-21: EN-DC_42_n28-n77 |
SoftBank Corp. |
R4-2008365 |
TP for TR 37.716-21-21: DC_2A_n38A-n78A |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2008366 |
TP for TR 37.716-21-21: DC_66A_n38A-n78A |
Huawei, HiSilicon, Bell Mobility, TELUS |
R4-2008367 |
TP for TR 37.716-21-21: DC_1A_n75A-n78A\DC_1A_n75A-n78(2A) |
Huawei, HiSilicon, CKH IOD UK |
R4-2008368 |
TP for TR 37.716-21-21: DC_3A_n75A-n78A\DC_3A_n75A-n78(2A) |
Huawei, HiSilicon, CKH IOD UK |
R4-2008369 |
TP for TR 37.716-21-21: DC_(n)41AA-n78A\DC_(n)41CA-n78A\DC_(n)41DA-n78A |
Huawei, HiSilicon,Etisalat |
8.7.3 |
EN-DC including NR inter CA with FR2 band [DC_R16_xBLTE_2BNR_yDL2UL-Core] |
|
R4-2006398 |
TP for TR 37.716-21-21 DC_1_n28-n257 |
Samsung, KDDI |
R4-2006399 |
TP for TR 37.716-21-21 DC_1-3_n28-n257 |
Samsung, KDDI |
R4-2006400 |
TP for TR 37.716-21-21 DC_1-3-41_n77-n257 |
Samsung, KDDI |
R4-2006401 |
TP for TR 37.716-21-21 DC_1-3-41-42_n77-n257 |
Samsung, KDDI |
R4-2006402 |
TP for TR 37.716-21-21 DC_1-3-42_n77-n257 |
Samsung, KDDI |
R4-2006403 |
TP for TR 37.716-21-21 DC_1-41_n28-n257 |
Samsung, KDDI |
R4-2006404 |
TP for TR 37.716-21-21 DC_1-41_n77-n257 |
Samsung, KDDI |
R4-2006405 |
TP for TR 37.716-21-21 DC_1-41-42_n77-n257 |
Samsung, KDDI |
R4-2006406 |
TP for TR 37.716-21-21 DC_3_n28-n257 |
Samsung, KDDI |
R4-2006407 |
TP for TR 37.716-21-21 DC_3-41_n28-n257 |
Samsung, KDDI |
R4-2006408 |
TP for TR 37.716-21-21 DC_3-41_n77-n257 |
Samsung, KDDI |
R4-2006409 |
TP for TR 37.716-21-21 DC_3-41-42_n77-n257 |
Samsung, KDDI |
R4-2006411 |
TP for TR 37.716-21-21 DC_18-41_n3-n257 |
Samsung, KDDI |
R4-2006414 |
TP for TR 37.716-21-21 DC_41_n3-n257 |
Samsung, KDDI |
R4-2006415 |
TP for TR 37.716-21-21 DC_41_n28-n257 |
Samsung, KDDI |
R4-2006416 |
TP for TR 37.716-21-21 DC_41_n77-n257 |
Samsung, KDDI |
R4-2006417 |
TP for TR 37.716-21-21 DC_41-42_n77-n257 |
Samsung, KDDI |
R4-2006623 |
Draft CR for 38.101-3: Support of n78C in the DC configurations including 1, 3, 5, 7, n78 and n257 |
SK Telecom |
R4-2006669 |
Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-8-11_n77-n257 |
SoftBank Corp. |
8.8.1 |
Rapporteur Input (WID/TR/CR) [NR_SUL_combos_R16-Core/Per] |
|
R4-2008066 |
Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
R4-2008067 |
TR 37.716-00-00 v0.7.0 |
Huawei, HiSilicon |
R4-2008068 |
CR on Introduction of completed SUL band combinations into TS 38.101-1 |
Huawei, HiSilicon |
R4-2008070 |
CR for 38.101-3: to clean up for SUL band combinations |
Huawei, HiSilicon |
8.8.2 |
UE RF [NR_SUL_combos_R16-Core] |
|
R4-2006948 |
Endorsed CR to 38307 on applicable SUL requirements |
Huawei, HiSilicon |
R4-2008069 |
TP for TR 37.716-00-00 for SUL_n41A-n95A |
Huawei, HiSilicon |
R4-2008071 |
Draft CR for 38.101-1 to correct UL configuration for SUL band combinations |
Huawei, HiSilicon |
R4-2008370 |
TP for TR 37.716-00-00 for SUL_n41A-n95A |
Huawei, HiSilicon |
R4-2008371 |
Draft CR for 38.101-1 to correct UL configuration for SUL band combinations |
Huawei, HiSilicon |
8.9.1 |
Rapporteur Input (WID/TR/CR) [NR_CA_R16_3BDL_1BUL-Core/Per] |
|
R4-2006281 |
Revised WID on Rel-16 NR inter-band CA for 3 bands DL with 1 band UL |
CATT |
R4-2006283 |
TR 38.716-03-01 0.8.0 |
CATT |
R4-2006284 |
Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 |
CATT |
R4-2006285 |
Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-3 |
CATT |
8.9.2 |
UE RF [NR_CA_R16_3BDL_1BUL-Core] |
|
R4-2006068 |
Correction to n29-n66-n70 CA combination |
Dish Network |
R4-2006832 |
TP for TR 38.716-03-01: UE requirements for CA_n1A-n78A-n257A |
CHTTL |
R4-2006839 |
TP for TR 38.716-03-01: UE requirements for CA_n1A-n78A-n257A |
CHTTL |
R4-2006913 |
CR to TS 38.101-3 on corrections to 3BDL and 1BUL inter-band CA configurations between FR1 and FR2 (Rel-16) |
ZTE Corporation |
R4-2007627 |
TP for TR 38.716-03-01 to include CA_n1-n3-n7 |
Ericsson, Telstra, BT plc |
R4-2007628 |
TP for TR 38.716-03-01 to include CA_n3-n7-n28 |
Ericsson, Telstra |
R4-2007629 |
TP for TR 38.716-03-01 to include CA_n3-n7-n78 |
Ericsson, Telstra, BT plc |
R4-2007630 |
TP for TR 38.716-03-01 to include CA_n7-n28-n78 |
Ericsson, Telstra |
8.10.1 |
Rapporteur Input (WID/TR/CR) [NR_CA_R16_4BDL_1BUL-Core/Per] |
|
R4-2006047 |
TR 38.716-04-01 v0.5.0 Rel-16 NR Inter-band 4 bands CA |
Ericsson |
R4-2007599 |
Revised WID 4 bands NR CA Rel-16 |
Ericsson |
R4-2007608 |
CR introduction completed band combinations 38.716-04-01 - |
Ericsson |
R4-2007609 |
CR introduction completed band combinations 38.716-04-01 - |
Ericsson |
8.10.2 |
UE RF [NR_CA_R16_4BDL_1BUL-Core] |
|
R4-2006611 |
TP to TR 38.716-04-01 for CA_n7-n25-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2007631 |
TP for TR 38.716-04-01 to include CA_n1-n3-n7-n28 |
Ericsson, Telstra |
R4-2007632 |
TP for TR 38.716-04-01 to include CA_n1-n3-n7-n78 |
Ericsson, Telstra |
R4-2007633 |
TP for TR 38.716-04-01 to include CA_n3-n7-n28-n78 |
Ericsson, Telstra |
8.11.1 |
Rapporteur Input (WID/TR/CR) [NR_CADC_R16_3BDL_2BUL-Core/Per] |
|
R4-2006873 |
TR 38.716-03-02 v070 |
ZTE Wistron Telecom AB |
R4-2007556 |
CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into Rel16 TS 38.101-1 |
ZTE Corporation |
R4-2007557 |
CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into Rel16 TS 38.101-3 |
ZTE Corporation |
R4-2007558 |
Revised WID on Rel-16 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL |
ZTE Corporation |
8.11.2 |
UE RF [NR_CADC_R16_3BDL_2BUL-Core] |
|
R4-2006607 |
TP to TR 38.716-03-02 for CA_n7-n25-n66 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2006608 |
TP to TR 38.716-03-02 for CA_n7-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2006609 |
TP to TR 38.716-03-02 for CA_n25-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2006610 |
TP to TR 38.716-03-02 for CA_n5-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2006929 |
TP for TR 38.716-03-02 CA_n1A-n3A-n78A with 2UL |
China Telecom |
R4-2008037 |
TP for TR 38.716-03-02: CA_n28A-n41A-n78A with two UL bands |
Huawei, HiSilicon,Etisalat |
R4-2008372 |
TP to TR 38.716-03-02 for CA_n7-n25-n66 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2008373 |
TP to TR 38.716-03-02 for CA_n7-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2008374 |
TP to TR 38.716-03-02 for CA_n25-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2008375 |
TP for TR 38.716-03-02: CA_n28A-n41A-n78A with two UL bands |
Huawei, HiSilicon,Etisalat |
8.12.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_LTE_NR_3DL3UL-Core/Per] |
|
R4-2007022 |
Revised WID on Rel-16 Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL |
ZTE Corporation |
R4-2007023 |
CR to reflect the completed ENDC combinations for 3 bands DL with 3 bands UL into Rel16 TS 38.101-3 |
ZTE Corporation |
R4-2007024 |
TR 37.716-33 v0.3.0: Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL |
ZTE Corporation |
8.12.2 |
UE RF [DC_R16_LTE_NR_3DL3UL-Core] |
|
R4-2007015 |
TP for TR37.716-33_ DC_3A_n40A-n258A |
ZTE Corporation |
8.13.1 |
Rapporteur Input (WID/TR/CR) [DC_R16_xBLTE_2BNR_yDL3UL-Core/Per] |
|
R4-2006992 |
Revised WID Dual Connectivity (EN-DC) of LTE inter-band CA xDL1UL bands (x=2,3,4) and NR FR1 1DL1UL band and NR FR2 1DL1UL band |
NTT DOCOMO INC. |
R4-2006994 |
Updated TR 37.716-41-22 |
NTT DOCOMO INC. |
R4-2006995 |
CR for introduce new EN-DC of LTE 2,3,4 band + NR FR1 1UL/1DL band + NR FR2 1UL/1DL band for TS 38.101-3 |
NTT DOCOMO INC. |
8.14 |
29dBm UE Power Class for B41 and n41 [LTE_NR_B41_Bn41_PC29dBm] |
|
R4-2008320 |
Email discussion summary for [95e][130] LTE_NR_B41_Bn41_PC29dBm |
Moderator (T-Mobile USA) |
R4-2008902 |
WF on additional measurements for 29 dBm MPR/A-MPR for UL MIMO and TxD |
T-Mobile USA |
R4-2008958 |
Email discussion summary for [95e][130] LTE_NR_B41_Bn41_PC29dBm |
Moderator (T-Mobile USA) |
8.14.1 |
Rapporteur Input (WID/TR/CR) [LTE_NR_B41_Bn41_PC29dBm] |
|
R4-2006643 |
Revised WID for 29 dBm UE Power Class for LTE Band 41and NR Band n41 |
T-Mobile USA |
8.14.2 |
UE RF (36.101, 38.101-1, 38.101-3) [LTE_NR_B41_Bn41_PC29dBm] |
|
R4-2006346 |
PC1.5 UL MIMO |
Apple Inc. |
R4-2006639 |
[29dBm] RIMD impact on EVM and MPR for UL MIMO and Tx Diversity |
Skyworks Solutions Inc. |
R4-2006644 |
CR for 38.101-1: Introduction of Power Class 1.5 |
T-Mobile USA |
R4-2006645 |
CR for 38.101-3: Introduction of Power Class 1.5 |
T-Mobile USA |
R4-2006647 |
LS to RAN4 on New UE capabilities for Power Class 1.5 |
T-Mobile USA |
R4-2006648 |
29 dBm Power Class number revisited |
T-Mobile USA |
R4-2006752 |
CR for Alloc_aware_ENDC_MPR for 38.101-3 |
CMCC |
R4-2006794 |
Remaining issues for Rel-16 B41/n41 intra-band EN-DC requirements |
LG Electronics Polska |
R4-2006795 |
Analysis of MPR and EVM based on reverse IMD for PC1.5 UL-MIMO |
LG Electronics Polska |
R4-2006796 |
CR for NS_04 A-MPR for B41n41 intra-band EN-DC in Rel-16 |
LG Electronics Polska |
R4-2006897 |
Clarification of 29dBm transmission for EN-DC UE |
KDDI Corporation |
R4-2008117 |
A-MPR for PC2/1.5 EN-DC |
Qualcomm Incorporated |
R4-2008204 |
MPR and NS_04 A-MPR for 29 dBm UL-MIMO |
T-Mobile USA Inc. |
R4-2008330 |
Analysis of MPR and EVM based on reverse IMD for PC1.5 UL-MIMO |
LG Electronics Polska |
R4-2008903 |
CR for Alloc_aware_ENDC_MPR for 38.101-3 |
CMCC |
R4-2008904 |
CR for 38.101-3: Introduction of Power Class 1.5 |
T-Mobile USA |
R4-2008906 |
LS to RAN2 on New UE capabilities for Power Class 1.5 |
RAN4 |
R4-2008974 |
A-MPR for PC2/1.5 EN-DC |
Qualcomm Incorporated |
8.14.3 |
Others [LTE_NR_B41_Bn41_PC29dBm] |
|
R4-2006646 |
CR for 38.307: Introduction of Power Class 1.5 |
T-Mobile USA |
R4-2008905 |
CR for 38.307: Introduction of Power Class 1.5 |
T-Mobile USA |
8.15 |
Power Class 2 UE for EN-DC (1 LTE FDD band +1 NR TDD band) [ENDC_UE_PC2_FDD_TDD-Core] |
|
R4-2008321 |
Email discussion summary for [95e][131] ENDC_UE_PC2_FDD_TDD |
Moderator (China Unicom) |
R4-2008907 |
WF on PC2 EN-DC FDD+TDD HPUE |
China Unicom |
R4-2008959 |
Email discussion summary for [95e][131] ENDC_UE_PC2_FDD_TDD |
Moderator (China Unicom) |
8.15.1 |
General [ENDC_UE_PC2_FDD_TDD-Core] |
|
R4-2006379 |
Further consideration on remaining issues from PC2 FDD-TDD ENDC |
Samsung |
R4-2006381 |
Discussion on the remain issues for NSA high power UE |
Xiaomi |
R4-2006614 |
On proceeding of EN-DC PC2 FDD + TDD HPUE |
China Unicom |
R4-2006843 |
Further discussion on blind scheme of FDD-TDD EN-DC High Power UE |
CHTTL |
R4-2008228 |
On FDD_TDD EN-DC HPUE |
Huawei, HiSilicon |
R4-2008264 |
CR for adding SAR solutions for FDD+TDD EN-DC PC2 UE |
vivo |
8.15.2 |
UE RF requirement [ENDC_UE_PC2_FDD_TDD-Core] |
|
R4-2006380 |
Draft CR for TS 38.101-3 to introduce power class for PC2 FDD-TDD ENDC |
Samsung |
R4-2006382 |
MSD analysis on high power UE for DC_3_n41 |
Xiaomi |
R4-2006654 |
UE based SAR control for Power Class 2 EN-DC FDD+TDD |
T-Mobile USA |
R4-2007008 |
Discussion on MSD for HPUE 3+n41 |
ZTE Corporation |
R4-2007052 |
EN-DC Power Class 2 for FDD-TDD band combinations without required CG coordination |
Ericsson |
R4-2007053 |
Introduction of EN-DC power class 2 for FDD-TDD band combinations |
Ericsson |
8.15.3 |
Signaling [ENDC_UE_PC2_FDD_TDD-Core] |
|
R4-2008262 |
On EN-DC (FDD+TDD) HPUE fall back schemes |
vivo |
R4-2008263 |
Draft LS on UE capability for PC2 inter-band EN-DC (LTE FDD+NR TDD) |
vivo |
8.16 |
Introduction of NR band n259 [NR_n259] |
|
R4-2007800 |
Updated TR 38.887 |
Ericsson |
R4-2008322 |
Email discussion summary for [95e][132] NR_n259 |
Moderator (Ericsson) |
R4-2008960 |
Email discussion summary for [95e][132] NR_n259 |
Moderator (Ericsson) |
R4-2008969 |
Updated TR 38.887 |
Ericsson |
8.16.1 |
UE RF (38.101-2) [NR_n259-Core] |
|
R4-2006990 |
CR for the introduction of n259 |
NTT DOCOMO INC. |
R4-2007087 |
EESS protection of n259 UE RF requirements |
OPPO |
R4-2007793 |
TP to TR 38.887 on UE RF requirements |
Ericsson |
R4-2007795 |
CR to 38.101-2 for Introduction of band n259 |
Ericsson |
R4-2008908 |
CR to 38.101-2 for Introduction of band n259 |
Ericsson |
R4-2009153 |
CR to 38.101-2 for Introduction of band n259 |
Ericsson |
8.16.2 |
BS RF (38.104) [NR_n259-Core] |
|
R4-2007792 |
TP to TR 38.887 on BS RF requirements |
Ericsson |
R4-2007796 |
CR to 38.141-2 for Introduction of band n259 |
Ericsson |
R4-2007797 |
CR to 38.104 for Introduction of band n259 |
Ericsson |
R4-2008909 |
CR to 38.141-2 for Introduction of band n259 |
Ericsson |
R4-2008975 |
CR to 38.104 for Introduction of band n259 |
Ericsson |
8.16.3 |
RRM (38.133) [NR_n259-Core] |
|
R4-2007794 |
TP to TR 38.887 on RRM |
Ericsson |
R4-2007798 |
CR to 38.133 for Introduction of band n259 |
Ericsson |
R4-2008910 |
TP to TR 38.887 on RRM |
Ericsson |
R4-2008911 |
CR to 38.133 for Introduction of band n259 |
Ericsson |
8.17 |
Adding 25MHz and 50MHz channel bandwidth in NR band n1 [NR_n1_BW2] |
|
R4-2008323 |
Email discussion summary for [95e][133] NR_BW |
Moderator (Ericsson) |
R4-2008961 |
Email discussion summary for [95e][133] NR_BW |
Moderator (Ericsson) |
8.17.1 |
UE RF (38.101-1) [NR_n1_BW2-Core] |
|
R4-2007324 |
CR for TS 38.101: adding 50 MHz CBW for n1 |
Huawei, HiSilicon, China unicom |
R4-2008912 |
CR for TS 38.101: adding 50 MHz CBW for n1 |
Huawei, HiSilicon, China unicom |
8.17.2 |
BS RF (38.104) [NR_n1_BW2-Core] |
|
R4-2007325 |
CR for TS 38.104: adding 50 MHz CBW for n1 |
Huawei, HiSilicon, China unicom |
8.18 |
LTE/NR spectrum sharing in band 48/n48 frequency range [NR_n48_LTE_48_coex-Core] |
|
R4-2008324 |
Email discussion summary for [95e][134] NR_n48_LTE_48_coex |
Moderator (Apple) |
R4-2008962 |
Email discussion summary for [95e][134] NR_n48_LTE_48_coex |
Moderator (Apple) |
8.18.2 |
Channel raster, sync raster, and UL shift [NR_n48_LTE_48_coex-Core] |
|
R4-2006336 |
LTE/NR spectrum sharing in band 48/n48 frequency range (channel raster) |
Apple Inc. |
R4-2006337 |
LTE/NR spectrum sharing in band 48/n48 frequency range (UL shift) |
Apple Inc. |
R4-2006338 |
LTE/NR spectrum sharing in band 48/n48 frequency range (sync pattern) |
Apple Inc. |
R4-2006588 |
Views on band 48/n48 spectrum sharing |
Nokia, Nokia Shanghai Bell |
R4-2006871 |
Views on dynamic spectrum sharing between LTE band 48 and NR band n48 |
Google Inc. |
R4-2007086 |
DSS in band n48 |
OPPO |
R4-2007441 |
On LTE/NR spectrum sharing in band 48/n48 |
Intel Corporation |
R4-2007791 |
UL shift for LTE/NR spectrum sharing in band 48/n48 |
Ericsson |
R4-2008288 |
LTE/NR spectrum sharing in band 48/n48 frequency range (channel raster) |
Apple Inc. |
R4-2008289 |
LTE/NR spectrum sharing in band 48/n48 frequency range (sync pattern) |
Apple Inc. |
8.19.1 |
UE RF (38.101-1) [NR_n3_BW] |
|
R4-2007506 |
CR to TS 38.101-1 - Add 40 MHz CBW in band n3 |
Ericsson |
R4-2007569 |
CR to TS 38.101-1 - Add 40 MHz CBW in band n3 |
Ericsson |
R4-2007879 |
Band n65 |
Ericsson |
R4-2008134 |
[NR_n3] 40MHz REFSENS Measurements |
Skyworks Solutions Inc. |
R4-2008913 |
CR to TS 38.101-1 - Add 40 MHz CBW in band n3 |
Ericsson |
8.19.2 |
BS RF (38.104) [NR_n3_BW] |
|
R4-2007505 |
CR to TS 38.104 - Add 40 MHz CBW in band n3 |
Ericsson |
8.20.1 |
UE RF (38.101-1) [NR_n65_BW] |
|
R4-2007508 |
CR to TS 38.101-1 - Add 50 MHz CBW in band n65 |
Ericsson |
R4-2007570 |
CR to TS 38.101-1 - Add 50 MHz CBW in band n65 |
Ericsson |
R4-2008133 |
[NR_n65_BW] Back-off Measurements |
Skyworks Solutions Inc. |
R4-2008914 |
CR to TS 38.101-1 - Add 50 MHz CBW in band n65 |
Ericsson |
8.20.2 |
BS RF (38.104) [NR_n65_BW] |
|
R4-2007507 |
CR to TS 38.104 - Add 50 MHz CBW in band n65 |
Ericsson |
9.1.1 |
General [FS_NR_MIMO_OTA_test] |
|
R4-2006307 |
TR38.827 v1.4.0 NR MIMO OTA |
CAICT |
R4-2006308 |
TP to TR 38.827 v1.3.0 on RMC |
CAICT |
R4-2006440 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2008715 |
Email discussion summary for [95e][326] FS_NR_MIMO_OTA_test |
Moderator (CAICT) |
R4-2008865 |
WF on FR2 MIMO OTA |
CAICT |
R4-2009047 |
Email discussion summary for [95e][326] FS_NR_MIMO_OTA_test |
Moderator (CAICT) |
9.1.2 |
Performance metrics [FS_NR_MIMO_OTA_test] |
|
R4-2006310 |
FR1 MIMO OTA measurement results |
CAICT |
R4-2006431 |
Discussion on SNR analysis for FR2 3D-MPAC |
Samsung |
9.1.3.2 |
FR2 test methodologies [FS_NR_MIMO_OTA_test] |
|
R4-2006740 |
FR2 Quality of Quiet Zone Procedure |
Keysight Technologies UK Ltd |
R4-2006741 |
On FR2 PSP Validation |
Keysight Technologies UK Ltd |
R4-2006742 |
TP to 38.827 to add PSP validation procedure |
Keysight Technologies UK Ltd, Spirent Communications |
R4-2006743 |
On FR2 3D MPAC Ambiguities and Blocking |
Keysight Technologies UK Ltd |
R4-2007084 |
Dynamic testing for FR2 |
OPPO |
R4-2007085 |
Uplink communication path placement for FR2 3D-MPAC |
OPPO |
R4-2007285 |
FR2 MIMO-OTA Test Methodologies |
Qualcomm Incorporated |
R4-2007563 |
TP to TR38.827 on FR2 test procedure |
Qualcomm Incorporated |
R4-2007592 |
PSP validation discussion |
Spirent Communications |
R4-2007594 |
TP on Verification of Channel Model implementation in TR38.827, PSP |
Spirent Communications |
R4-2007658 |
DUT relative orientation to channel model |
ROHDE & SCHWARZ |
R4-2008273 |
TP to TR38.827 to avoid ambiguities for FR2 MIMO OTA Testing |
Keysight Technologies UK Ltd |
R4-2008866 |
TP to TR38.827 on FR2 test procedure |
Qualcomm Incorporated |
9.2 |
Study on 7-24GHz frequency range [FS_7to24GHz_NR] |
|
R4-2008325 |
Email discussion summary for [95e][135] FS_7to24GHz_NR |
Moderator (Huawei) |
R4-2008963 |
Email discussion summary for [95e][135] FS_7to24GHz_NR |
Moderator (Huawei) |
9.2.1 |
General [FS_7to24GHz_NR] |
|
R4-2008138 |
TP to TR 38.820: editorial cleanup |
Huawei |
R4-2008915 |
TP to TR 38.820: editorial cleanup |
Huawei |
R4-2009161 |
Draft TR 38.820 v1.4.0 |
Huawei |
9.2.2 |
Regulatory survey [FS_7to24GHz_NR] |
|
R4-2008140 |
TP to TR 38.820: clarification on WRC-19 resolution for IMT for fixed wireless broadband in fixed services bands |
Huawei |
9.2.3 |
Deployment scenarios [FS_7to24GHz_NR] |
|
R4-2008139 |
TP to TR 38.820: deployment scenarios cleanup |
Huawei |
R4-2008916 |
TP to TR 38.820: deployment scenarios cleanup |
Huawei |
9.2.6.2 |
NR BS architecture [FS_7to24GHz_NR] |
|
R4-2006925 |
TP to TR 38.820: Addition of antenna parameter selection guideline in subclause 7.2.3 |
Ericsson |
R4-2008917 |
TP to TR 38.820: Addition of antenna parameter selection guideline in subclause 7.2.3 |
Ericsson |
9.2.6.3 |
TX requirements [FS_7to24GHz_NR] |
|
R4-2006105 |
TP to TR 38.820: Summary Tables for Transmitter Requirements |
Nokia, Nokia Shanghai Bell |
R4-2006106 |
TP to TR 38.820: Summary Tables for Receiver Requirements |
Nokia, Nokia Shanghai Bell |
R4-2008918 |
TP to TR 38.820: Summary Tables for Transmitter Requirements |
Nokia, Nokia Shanghai Bell |
R4-2008919 |
TP to TR 38.820: Summary Tables for Receiver Requirements |
Nokia, Nokia Shanghai Bell |
10.1 |
Introduction of FR2 FWA UE with maximum TRP of 23dBm for band n257 and n258 [NR_FR2_FWA_Bn257_Bn258] |
|
R4-2008326 |
Email discussion summary for [95e][136] NR_FR2_FWA_Bn257_Bn258 |
Moderator (Softbank) |
R4-2008920 |
LS to RAN2 on FR2 FWA options |
SoftBank |
R4-2008921 |
WF on FR2 FWA evaluations |
Qualcomm |
R4-2008922 |
WF on FR2 FWA RF requirements |
Huawei |
R4-2008964 |
Email discussion summary for [95e][136] NR_FR2_FWA_Bn257_Bn258 |
Moderator (Softbank) |
10.1.1 |
UE RF (38.101-2) [NR_FR2_FWA_Bn257_Bn258] |
|
R4-2006432 |
Discussion on new FR2 FWA UE |
Samsung |
R4-2006703 |
Spherical EIRP EIS of FR2 FWA UE with maximum TRP of 23dBm |
MediaTek Beijing Inc. |
R4-2006705 |
MBR of FR2 FWA UE with maximum TRP of 23dBm |
MediaTek Beijing Inc. |
R4-2006776 |
FR2 23dBm FWA pk. EIRP and REFSENS budgets |
Qualcomm Incorporated |
R4-2007106 |
On power class definition for FR2 FWA UE |
Ericsson |
R4-2007110 |
UE RF requirements for new FR2 FWA use case |
Intel Corporation |
R4-2008006 |
Power class on new FR2 FWA UE |
Nokia, Nokia Shanghai Bell |
R4-2008007 |
Beam correspondence requirement on FR2 FWA UE |
Nokia, Nokia Shanghai Bell |
R4-2008008 |
Multiband relaxation for FWA UE |
Nokia, Nokia Shanghai Bell |
R4-2008175 |
on new FR2 FWA UE requirement |
Huawei, HiSilicon |
R4-2008274 |
New power class feature for FWA |
NTT DOCOMO INC. |
10.1.3 |
RRM (38.133) [NR_FR2_FWA_Bn257_Bn258] |
|
R4-2007134 |
RRM Requirements for the new FWA device with 23dBm TRP |
Qualcomm Incorporated |
R4-2007804 |
Discussion on RRM impact due to introduction of new FR2 FWA UE |
Huawei, HiSilicon |
R4-2008523 |
Email discussion summary for [95e][234] NR_FR2_FWA_Bn257_Bn258_RRM |
Moderator (Huawei, HiSilicon) |
R4-2008663 |
approved |
Huawei, HiSilicon |
R4-2009096 |
Email discussion summary for [95e][234] NR_FR2_FWA_Bn257_Bn258_RRM |
Moderator (Huawei, HiSilicon) |
10.2 |
Introduction of NR band n13 [NR_n13] |
|
R4-2008327 |
Email discussion summary for [95e][137] NR_n13 |
Moderator (Huawei) |
R4-2008965 |
Email discussion summary for [95e][137] NR_n13 |
Moderator (Huawei) |
10.2.1 |
UE RF (38.101-1) [NR_n13-Core] |
|
R4-2007311 |
Draft CR to TS 38.101-1: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2008209 |
n13 AMPR |
Qualcomm Incorporated |
10.2.2 |
BS RF (38.104) [NR_n13-Core] |
|
R4-2007312 |
Draft CR to TS 38.104: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2008923 |
Draft CR to TS 38.104: introduction of NR band n13 |
Huawei, HiSilicon |
11.1 |
Study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz [FS_6425_10500MHz _NR] |
|
R4-2008328 |
Email discussion summary for [95e][138] FS_6425_10500MHz _NR |
Moderator (Ericsson) |
R4-2008924 |
LS to Parameters of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-23 (below 5 GHz) |
RAN4 |
R4-2008925 |
WF on BS and UE IMT parameters for the SI on 6.425-7.125GHz and 10.0-10.5GHz |
CATT |
R4-2008926 |
WF on BS Antenna parameters for the SI on 6.425-7.125GHz and 10.0-10.5GHz |
Huawei |
R4-2008927 |
WF on Simulation Assumptions for the SI on 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Ericsson, ZTE |
R4-2008966 |
Email discussion summary for [95e][138] FS_6425_10500MHz _NR |
Moderator (Ericsson) |
R4-2009151 |
WF on BS and UE IMT parameters for the SI on 6.425-7.125GHz and 10.0-10.5GHz |
CATT |
11.1.1 |
UE parameters |
|
R4-2006286 |
BS parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
CATT |
R4-2007306 |
UE IMT technology related parameters |
Huawei, HiSilicon |
R4-2007511 |
SI on IMT parameters - UE parameters for 6.425-7.025GHz / 7.025-7.125 / 10.0 |
Ericsson |
R4-2007514 |
TP to TR for SI on IMT parameters - UE parameters |
Ericsson |
11.1.2 |
BS parameters |
|
R4-2006287 |
UE parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
CATT |
R4-2007307 |
BS IMT technology related parameters |
Huawei, HiSilicon |
R4-2007510 |
SI on IMT parameters - BS parameters for 6.425-7.025GHz / 7.025-7.125 / 10.0 |
Ericsson |
R4-2007513 |
TP to TR for SI on IMT parameters - BS parameters |
Ericsson |
11.1.3 |
Coexistence study |
|
R4-2006107 |
TP to TR 38.9xx: System level simulation methodology and assumptions for study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2006108 |
Urban Macro Downlink Coexistence Simulation Results for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2006109 |
Indoor Downlink Coexistence Simulation Results for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2007308 |
TP on co-existence simulation assumption on 6.425-7.125GHz and 10.0-10.5GHz |
Huawei, HiSilicon |
R4-2007394 |
Discussion on simulation assumption for 6425-7125MHz and 10-10.5GHz |
ZTE Corporation |
R4-2007395 |
Simulation results for 6425-7125MHz and 10-10.5GHz |
ZTE Corporation |
R4-2007509 |
SI on IMT parameters - simulation assumptions |
Ericsson |
R4-2007512 |
TP to TR for SI on IMT parameters - simulation assumptions |
Ericsson |
R4-2008095 |
Dense Urban Downlink Coexistence Simulation Results for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2008928 |
TP to TR 38.9xx: System level simulation methodology and assumptions for study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
11.1.4 |
Antenna characteristics |
|
R4-2006110 |
AAS BS antenna characteristics for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2006288 |
Antenna characteristics |
CATT |
R4-2006924 |
Array antenna model parameters |
Ericsson |
R4-2007309 |
Antenna characteristics on 6.425-7.025GHz, 7.025-7.125GHz and 10.0-10.5 GHz |
Huawei, HiSilicon |
R4-2007393 |
Discussion on NR BS antenna parameters |
ZTE Corporation |
11.2 |
Reply of IMT parameters for other frequency ranges requested in RP-200042 |
|
R4-2006111 |
AAS BS antenna characteristics for frequency ranges below 6GHz |
Nokia, Nokia Shanghai Bell |
R4-2006289 |
Open issue on IMT parameters for other frequency ranges below 6GHz |
CATT |
R4-2006761 |
discussion on the remaining issues for IMT parameters below 6GHz spectrum |
CMCC |
R4-2006923 |
Array antenna model parameters |
Ericsson |
R4-2007089 |
Reply of IMT parameters for frequency ranges below 6GHz |
OPPO |
R4-2007310 |
IMT parameters for other frequency ranges below 5 GHz |
Huawei, HiSilicon |
R4-2008111 |
Draft LS to Parameters of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-23 (below 6 GHz) |
Ericsson |
12.1 |
BS RF [WI code or TEI] |
|
R4-2006112 |
CR to TS 36.141: Corrections on table note index for test models |
Nokia, Nokia Shanghai Bell |
R4-2006113 |
CR to TS 36.141: Corrections on table note index for test models |
Nokia, Nokia Shanghai Bell |
R4-2006114 |
CR to TS 36.141: Corrections on table note index for test models |
Nokia, Nokia Shanghai Bell |
R4-2007474 |
CR to TS 37.107 with correction to interfering signal for conformance test for energy detection accuracy to align withTS 37.213 |
Nokia, Nokia Shanghai Bell |
R4-2007475 |
Discussion on interfering signal for conformance test for ED accuracy for eLAA |
Nokia, Nokia Shanghai Bell |
R4-2008101 |
CR to 37.104 on Removal of TBD for NB-IoT (Rel-15) |
Ericsson |
R4-2008102 |
CR to 37.104 on Removal of TBD for NB-IoT (Rel-16) |
Ericsson |
R4-2008690 |
Email discussion summary for [95e][301] LTE_maintenance_RF_BS |
Moderator (Ericsson) |
R4-2008867 |
Email discussion summary for [95e][301] LTE_maintenance_RF_BS |
Moderator (Ericsson) |
R4-2008868 |
CR to TS 37.107 with correction to interfering signal for conformance test for energy detection accuracy to align withTS 37.213 |
Nokia, Nokia Shanghai Bell |
R4-2009048 |
WF on modifying the ED Threshold |
Nokia |
R4-2009053 |
CR to 36.104 on Removal of FFSs, brackets and TBD (Rel-15) |
Ericsson |
R4-2009054 |
CR to 36.104 on Removal of FFSs, brackets and TBD (Rel-16) |
Ericsson |
12.2 |
UE RF [WI code or TEI] |
|
R4-2006445 |
NBIOT standalone operation for FCC regulation considerations |
MediaTek Inc. |
R4-2006446 |
CR for TS 36.101: CR for category NB1 against FCC regulation in standalone mode |
MediaTek Inc. |
R4-2006447 |
CR for TS 36.101: CR for category NB1 against FCC regulation in standalone mode |
MediaTek Inc. |
R4-2006448 |
CR for TS 36.101: CR for category NB1 against FCC regulation in standalone mode |
MediaTek Inc. |
R4-2006449 |
CR for TS 36.101: CR for spec corrections for MSD table |
MediaTek Inc. |
R4-2006450 |
CR for TS 36.101: CR for spec corrections for MSD table |
MediaTek Inc. |
R4-2006599 |
Corrections of CA band combo table |
Nokia, Nokia Shanghai Bell |
R4-2006600 |
Corrections of CA band combo table |
Nokia, Nokia Shanghai Bell |
R4-2006651 |
CR for 36.101: fix modifiedMPRbehavior for NS_31 |
T-Mobile USA |
R4-2006652 |
CR for 36.101: fix modifiedMPRbehavior for NS_31 |
T-Mobile USA |
R4-2006653 |
Mirror CR for 36.101: fix modifiedMPRbehavior for NS_31 |
T-Mobile USA |
R4-2007564 |
Exclusion 100KHz for NB-IoT to meet FCC band-edge requirements |
Qualcomm Incorporated |
R4-2007589 |
CR to remove TBD and braket on CAT-M2 |
Ericsson |
R4-2007590 |
CR to remove TBD and braket on CAT-M2 Type A for Rel-15 |
Ericsson |
R4-2007591 |
CR to remove TBD and braket on CAT-M2 Type A for Rel-16 |
Ericsson |
R4-2008181 |
CR for 36.101 MPR for cat-NB Rel-13 |
Huawei, HiSilicon |
R4-2008182 |
CR for 36.101 MPR for cat-NB Rel-14 |
Huawei, HiSilicon |
R4-2008183 |
CR for 36.101 MPR for cat-NB Rel-15 |
Huawei, HiSilicon |
R4-2008184 |
CR for 36.101 MPR for cat-NB Rel-16 |
Huawei, HiSilicon |
R4-2008275 |
on cat-NB MPR for 3 tones and 6 tones allocation |
Huawei, HiSilicon |
R4-2008973 |
CR for 36.101 MPR for cat-NB Rel-13 |
Huawei, HiSilicon |
R4-2008977 |
CR to remove TBD for A-MPR for NS_33 in 36.101 Rel-14 |
Huawei, HiSilicon |
R4-2008978 |
CR to remove TBD for A-MPR for NS_33 in 36.101 Rel-15 |
Huawei, HiSilicon |
R4-2008979 |
CR to remove TBD for A-MPR for NS_33 in 36.101 Rel-16 |
Huawei, HiSilicon |
R4-2008980 |
NB IoT Maintenance for FCC Regulation |
MediaTek, Qualcomm |
R4-2008989 |
CR to remove TBD in in clause 6.6.3 in 36.101 Rel-15 |
Qualcomm |
R4-2009140 |
CR to remove TBD in in clause 6.6.3 in 36.101 Rel-16 |
Qualcomm |
R4-2009148 |
NB IoT Maintenance for FCC Regulation |
MediaTek, Qualcomm |
12.3 |
RRM [WI code or TEI] |
|
R4-2006082 |
CR to parameter for Cat-M RRM A.7.3.55 |
ANRITSU LTD |
R4-2006083 |
CR to parameter for Cat-M RRM A.7.3.55 |
ANRITSU LTD |
R4-2006084 |
CR to parameter for Cat-M RRM A.7.3.55 |
ANRITSU LTD |
R4-2006085 |
CR to parameter for Cat-M RRM A.7.3.55 |
ANRITSU LTD |
R4-2006086 |
CR to RRM MPDSCH Repetitions in CE ModeA test case |
ANRITSU LTD |
R4-2006087 |
CR to RRM MPDSCH Repetitions in CE ModeA test case |
ANRITSU LTD |
R4-2006088 |
CR to RRM MPDSCH Repetitions in CE ModeA test case |
ANRITSU LTD |
R4-2006089 |
CR to RRM MPDSCH Repetitions in CE ModeA test case |
ANRITSU LTD |
R4-2006966 |
Finalisation of requirements in 36.133 R15 |
Ericsson |
R4-2006967 |
Finalisation of requirements in 36.133 R16 |
Ericsson |
R4-2006968 |
Editorial correction of E-UTRAN FDD |
Ericsson |
R4-2006969 |
Editorial correction of E-UTRAN FDD |
Ericsson |
R4-2007118 |
Correction of subclause references in clause 5 |
Nokia, Nokia Shanghai Bell |
R4-2007146 |
Number of carriers to measure in euCA |
Nokia, Nokia Shanghai Bell |
R4-2007147 |
CR on Number of carriers to monitor for IDLE mode measurements |
Nokia, Nokia Shanghai Bell |
R4-2007148 |
CR on Number of carriers to monitor for IDLE mode measurements |
Nokia, Nokia Shanghai Bell |
R4-2007149 |
CR clarifying S-measure thresholds for EMR carriers |
Nokia, Nokia Shanghai Bell |
R4-2007150 |
CR clarifying S-measure thresholds for EMR carriers |
Nokia, Nokia Shanghai Bell |
R4-2007424 |
CR to TS 36.133: Change of SR-ConfigIndex in eMTC RLM DRX test cases (Rel-13) |
Rohde & Schwarz |
R4-2007425 |
CR to TS 36.133: Change of SR-ConfigIndex in eMTC RLM DRX test cases (Rel-14) |
Rohde & Schwarz |
R4-2007426 |
CR to TS 36.133: Change of SR-ConfigIndex in eMTC RLM DRX test cases (Rel-15) |
Rohde & Schwarz |
R4-2007427 |
CR to TS 36.133: Change of SR-ConfigIndex in eMTC RLM DRX test cases (Rel-16) |
Rohde & Schwarz |
R4-2007724 |
CR on NB-IoT cell reselection margin in enhanced coverage in Rel-13 |
Huawei, Hisilicon |
R4-2007725 |
CR on NB-IoT cell reselection margin in enhanced coverage in Rel-14 (Cat A) |
Huawei, Hisilicon |
R4-2007726 |
CR on NB-IoT cell reselection margin in enhanced coverage in Rel-15 (Cat A) |
Huawei, Hisilicon |
R4-2007727 |
CR on NB-IoT cell reselection margin in enhanced coverage in Rel-16 (Cat A) |
Huawei, Hisilicon |
R4-2007876 |
Correction to eMTC inter-frequency reselection margin R14 |
Huawei, HiSilicon |
R4-2007877 |
Correction to eMTC inter-frequency reselection margin R15 |
Huawei, HiSilicon |
R4-2007878 |
Correction to eMTC inter-frequency reselection margin R16 |
Huawei, HiSilicon |
R4-2008521 |
Email discussion summary for [95e][232] LTE_RRM_maintenance |
Moderator (Ericsson) |
R4-2008656 |
CR to TS 36.133: Change of SR-ConfigIndex in eMTC RLM DRX test cases (Rel-13) |
Rohde & Schwarz |
R4-2008657 |
Finalisation of requirements in 36.133 R15 |
Ericsson |
R4-2008658 |
Finalisation of requirements in 36.133 R16 |
Ericsson |
R4-2009094 |
Email discussion summary for [95e][232] LTE_RRM_maintenance |
Moderator (Ericsson) |
R4-2009107 |
Finalisation of requirements in 36.133 R16 |
Ericsson |
12.4 |
Demodulation and CSI [WI code or TEI] |
|
R4-2007213 |
CR: Updates to FeNB-IoT NPRACH TDD performance requirements in TS 36.104 (Rel-15) |
Huawei, HiSilicon |
R4-2007214 |
CR: Updates to FeNB-IoT NPRACH TDD performance requirements in TS 36.104 (Rel-16) |
Huawei, HiSilicon |
R4-2007215 |
CR: Updates to FeNB-IoT NPRACH TDD conformance testing in TS 36.141 (Rel-15) |
Huawei, HiSilicon |
R4-2007216 |
CR: Updates to FeNB-IoT NPRACH TDD conformance testing in TS 36.141 (Rel-16) |
Huawei, HiSilicon |
R4-2007217 |
Summary of simulation results for Rel-15 FeNB-IoT NPRACH TDD formats |
Huawei, HiSilicon |
R4-2007218 |
CR: Updates to FeNB-IoT UE performance requirements in 36.101 (Rel-15) |
Huawei, HiSilicon |
R4-2007219 |
CR: Updates to FeNB-IoT UE performance requirements in 36.101 (Rel-16) |
Huawei, HiSilicon |
R4-2007242 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-8) |
Huawei, HiSilicon |
R4-2007243 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-9) |
Huawei, HiSilicon |
R4-2007244 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-10) |
Huawei, HiSilicon |
R4-2007245 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-11) |
Huawei, HiSilicon |
R4-2007246 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-12) |
Huawei, HiSilicon |
R4-2007247 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-13) |
Huawei, HiSilicon |
R4-2007248 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-14) |
Huawei, HiSilicon |
R4-2007249 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-15) |
Huawei, HiSilicon |
R4-2007250 |
CR: Updates to LTE CQI test cases 9.2.1.7 and 9.2.1.8 (Rel-12) |
Huawei, HiSilicon |
R4-2007251 |
CR: Updates to LTE CQI test cases 9.2.1.7 and 9.2.1.8 (Rel-13) |
Huawei, HiSilicon |
R4-2007252 |
CR: Updates to LTE CQI test cases 9.2.1.7 and 9.2.1.8 (Rel-14) |
Huawei, HiSilicon |
R4-2007253 |
CR: Updates to LTE CQI test cases 9.2.1.7 and 9.2.1.8 (Rel-15) |
Huawei, HiSilicon |
R4-2007254 |
CR: Updates to LTE CQI test cases 9.2.1.7 and 9.2.1.8 (Rel-16) |
Huawei, HiSilicon |
R4-2007255 |
CR: Introduction for intra-band contiguous CA performance requirements for FDD with minimum channel spacing (Rel-15) |
Huawei, HiSilicon |
R4-2007256 |
CR: Introduction for intra-band contiguous CA performance requirements for FDD with minimum channel spacing (Rel-16) |
Huawei, HiSilicon |
R4-2007366 |
Simulation results on NB-IoT NPRACH demodulation performance for TDD |
Ericsson |
R4-2008755 |
CR: Updates to FeNB-IoT NPRACH TDD performance requirements in TS 36.104 (Rel-15) |
Huawei, HiSilicon |
R4-2008756 |
CR: Updates to FeNB-IoT NPRACH TDD conformance testing in TS 36.141 (Rel-15) |
Huawei, HiSilicon |
R4-2008757 |
CR: Correction on LTE SRS configuration for UL timing adjustment conformance testing (Rel-15) |
Huawei, HiSilicon |
13 |
Liaison and output to other groups |
|
R4-2006570 |
Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 |
Intel Corporation |
R4-2006625 |
Draft Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 (R2-2004267) |
Apple |
14.1 |
Simplification of band combinations in RAN4 specifications |
|
R4-2006626 |
Simplification of band combination tables in 38.101 |
Apple |
R4-2006734 |
Discussion about Band combination spreadsheet formats |
Futurewei |
R4-2006840 |
Considerations on simplification of EN-DC configuration including FR2 |
ZTE Corporation |
R4-2008064 |
On new format for band combinations |
Nokia, Nokia Shanghai Bell |
R4-2008085 |
Further discussion on improvement of request, SR and BC basket WID index table |
Huawei, HiSilicon |
R4-2008112 |
Simplification of band combinations |
NTT DOCOMO INC. |
R4-2008329 |
Email discussion summary for [95e][139] BC_simplification |
Moderator (NTT DOCOMO) |
R4-2008929 |
WF on refinement on excel format for band combinations |
Huawei, HiSilicon |
R4-2008930 |
WF on simplification on band combinations in specification |
ZTE |
R4-2008931 |
Simplification of band combinations |
NTT DOCOMO INC. |
R4-2008967 |
Email discussion summary for [95e][139] BC_simplification |
Moderator (NTT DOCOMO) |
R4-2009176 |
WF on simplification on band combinations in specification |
ZTE |
14.2.1 |
Basket WI approach for adding existing channel bandwidth on existing NR bands |
|
R4-2006933 |
UE bandwidths for SUL bands |
Huawei, HiSilicon |
R4-2007516 |
Motivation slides for the new basket WI adding existing channel BW support and the proposals included |
Ericsson |
R4-2007517 |
New basket WI adding existing channel BW support in existing NR bands |
Ericsson |
R4-2008250 |
Re-consideration of adding UE 100MHz channel bandwidth for n40 |
Huawei, HiSilicon |
14.2.2 |
Proposals on adding “brand new” channel bandwidth |
|
R4-2006339 |
Non-standard spectrum allocations for NR bands |
Apple Inc. |
R4-2006640 |
New SID: Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
T-Mobile USA |
R4-2006641 |
Motivation for new SID on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
T-Mobile USA |
R4-2006642 |
On efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
T-Mobile USA |
R4-2006812 |
Discussion on scalable solutions to handle brand new channel bandwidth |
CMCC |
R4-2008247 |
New WID proposal: introduction of brand new channel bandwidths for NR |
Huawei, HiSilicon |
14.2.3 |
Basket WIs for LTE CA, EN-DC, NR CA and NR DC |
|
R4-2006299 |
Rel-17 NR inter-band CA for 3 bands DL with 1 band UL |
CATT |
R4-2006736 |
New WID onon LTE x bands (xDL/1UL x=1.2,3,4) with NR 2 bands (2DL/1UL) EN DC in Rel-17 |
LG Electronics France |
R4-2006793 |
New WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics Polska |
R4-2006802 |
Proposal on new Rel-17 Basket: NR inter-band Carrier Aggregation and Dual connectivity for DL 4 bands and 2UL bands |
Samsung |
R4-2006898 |
New WID on Rel.17 EN-DC and NE-DC for 2 bands DL with 2 bands UL (1 LTE band + 1 NR band) |
CHTTL |
R4-2006930 |
New WID on Power Class 2 UE for NR inter-band CA and SUL band combination with 2 bands UL |
China Telecom |
R4-2006991 |
New WID: Dual Connectivity (EN-DC) of LTE inter-band CA xDL/1UL bands (x=2,3,4) and NR FR1 1DL/1UL band and NR FR2 1DL/1UL band |
NTT DOCOMO INC. |
R4-2007016 |
Proposed new WID on Rel-17 EN-DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) |
ZTE Corporation |
R4-2007017 |
Proposed new WID on Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
R4-2007018 |
Proposed new WID on Rel-17 Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL |
ZTE Corporation |
R4-2007169 |
Draft Rel-17 WID on Dual Connectivity (EN-DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL) |
Nokia, Nokia Shanghai Bell |
R4-2007340 |
New Rel-17 WID: Dual Connectivity (EN-DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
R4-2007499 |
Rel-17 WID on Dual Connectivity (DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL) |
Nokia, Nokia Shanghai Bell |
R4-2007559 |
Proposed new WID on Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL |
ZTE Corporation |
R4-2007565 |
New WID: Rel17 LTE inter-band CA for 2 bands DL with 1 band UL |
Qualcomm Incorporated |
R4-2007587 |
New WID on Additional LTE bands for UE category M1 and_or NB1 in Rel-17 |
Ericsson |
R4-2007588 |
New WID on Additional LTE bands for UE category M2 and_or NB2 in Rel-17 |
Ericsson |
R4-2007600 |
New WID Basket WI for LTE Intra-band CA Rel-17 |
Ericsson |
R4-2007601 |
New WID NR Intra-band Rel-17 |
Ericsson |
R4-2007602 |
New WID LTE 3DL and one NR band Rel-17 |
Ericsson |
R4-2007603 |
New WID 4 bands NR CA Rel-17 |
Ericsson |
R4-2008061 |
New WID: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5) with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2008087 |
New WI Rel-17 on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
R4-2008088 |
New WI Rel-17 NR inter-band CA for 5 bands DL with x bands UL (x=1, 2) |
Huawei, HiSilicon |
R4-2008186 |
new WID: Rel-17 LTE inter-band CA for 3 bands DL with 1 band UL |
Huawei, HiSilicon |
R4-2008236 |
New WID for Rel-17 LTE inter-band CA for 2 bands DL with 2 bands UL |
Huawei, HiSilicon |
R4-2009145 |
Proposed new WID on Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
R4-2009146 |
Proposed new WID on Rel-17 Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL |
ZTE Corporation |
R4-2009147 |
Proposed new WID on Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL |
ZTE Corporation |
R4-2009179 |
New Rel-17 WID: Dual Connectivity (EN-DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
R4-2009180 |
Rel-17 NR inter-band CA for 3 bands DL with 1 band UL |
CATT |
R4-2009291 |
Proposal on new Rel-17 Basket: NR inter-band Carrier Aggregation and Dual connectivity for DL 4 bands and 2UL bands |
Samsung |
14.2.4 |
Others |
|
R4-2006042 |
Motivation for further enhancement on NR demodulation performance requirements |
China Telecom |
R4-2006043 |
Draft WID: Further enhancement on NR demodulation performance requirements |
China Telecom |
R4-2006091 |
New WID proposal: Modification of LTE Band 24 specifications to comply with updated regulatory emission limits |
Ligado Networks |
R4-2006139 |
New WID proposal for Introduction of NR band n24 |
Ligado Networks |
R4-2006140 |
New WID: introduction of NR 47 GHz band |
T-Mobile USA Inc., Dish Network |
R4-2006201 |
Motivation paper on Rel-17 further RRM enhancement |
Apple |
R4-2006202 |
WID of R17 NR RRM further enhancement |
Apple |
R4-2006292 |
Study on support of unsynchronized operation between TDD bands |
CATT |
R4-2006300 |
Motivation on NR RRM requirement enhancement in Rel-17 |
CATT |
R4-2006301 |
New WID on NR RRM requirement enhancement in Rel-17 |
CATT |
R4-2006302 |
Motivation on basket WI on V2X band combination |
CATT |
R4-2006303 |
New basket WID: V2X band combination for supporting co-current operation between Uu frequency bands and V2X bands |
CATT |
R4-2006309 |
New WID on Verification of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of NR UEs |
CAICT |
R4-2006362 |
Further views on NR FR1 TRP/TRS |
Apple Inc. |
R4-2006363 |
FR2 RF enhancements for Rel-17 |
Apple Inc. |
R4-2006480 |
Motivation paper on R17 RRM enh |
MediaTek inc. |
R4-2006549 |
Motivation to introduce new SI of MG enhancement |
Intel Corporation, Apple |
R4-2006550 |
New SI Proposal Study on measurement gap enhancement |
Intel Corporation, Apple |
R4-2006613 |
FR2 for NR based Satellite networks |
HUGHES Network Systems Ltd |
R4-2006683 |
New SID on high-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12 and in Band 5 |
US Cellular Corporation |
R4-2006710 |
Motivation on NR RRM requirement for UE different RX beam sets in FR2 |
LG Electronics Inc. |
R4-2006739 |
New WID proposal on introduction of 1.6 GHz NR SUL band with same uplink frequency range of Band 24 |
Ligado Networks |
R4-2006753 |
Motivation for new WI on air-to-ground network for NR |
CMCC |
R4-2006754 |
New WID on air-to-ground network for NR |
CMCC |
R4-2006755 |
New WID on introduction of 1880-1920MHz SUL band for NR |
CMCC |
R4-2006756 |
New WID on introduction of 2300-2400MHz SUL band for NR |
CMCC |
R4-2006844 |
LTE / NR Spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2006894 |
Possible bands for NR based satellite networks |
THALES, HUGHES Network Systems Ltd, Intelsat |
R4-2006899 |
Motivation for WI: Verification of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of NR UEs |
CAICT |
R4-2007069 |
New SID on NR FR1 and EN-DC FR1 UE TRP and TRS |
OPPO |
R4-2007070 |
Motivation of NR FR1 TRP TRS new study item |
OPPO |
R4-2007257 |
New WID on UE performance for advanced recevier with soft IC for inter-stream interference and IRC for inter-cell interference |
Huawei, HiSilicon |
R4-2007258 |
Motivation paper of new WID on UE performance for advanced recevier with soft IC for inter-stream interference and IRC for inter-cell interference |
Huawei, HiSilicon |
R4-2007361 |
LTE/NR spectrum sharing in Band 38/n38 |
VODAFONE Group Plc |
R4-2007938 |
FR1 |
Intelsat |
R4-2008128 |
New WID: FR1/FR2 for NR based HAPS networks |
Intelsat LLC, Loon LLC, Google Inc. |
R4-2008142 |
FR1/FR2 |
Intelsat |
R4-2008248 |
New WID proposal: supporting overlapping CA for LTE |
Huawei, HiSilicon |
R4-2008249 |
Motivation on WID of further enhancement of FR1 RF requirement |
Huawei, HiSilicon |
R4-2008268 |
[draft] New SID: Optimizations on power class fall back |
vivo |
R4-2008269 |
Consideration on NR SISO OTA WI |
vivo |
R4-2008270 |
Motivation for NR FR1 UE TRP and TRS |
vivo, CMCC, CAICT, Rohde & Schwarz |
R4-2008271 |
New WID: NR FR1 UE SA and EN-DC TRP and TRS |
vivo, CMCC, CAICT, Rohde & Schwarz |
15.1 |
Views on workload management and meeting efficiency improvement |
|
R4-2006663 |
Consideration on potential e-meeting improvement |
ZTE Wistron Telecom AB |
R4-2008003 |
Proposals for Managing RAN4 work load |
Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Mediatek, Qualcomm, Verizon, AT&T, T-Mobile, Softbank, KDDI, NTT DoCoMo, Rohde & Schwarz, KT, SKT |
R4-2008004 |
Proposals to improve e-meeting efficiency |
Ericsson |
R4-2008060 |
Views on workload management and meeting efficiency improvement |
Nokia, Nokia Shanghai Bell |
16 |
Close of the E-meeting |
|
R4-2008790 |
Void |
ETSI MCC |
R4-2009068 |
Void |
ETSI MCC |
R4-2009069 |
Void |
ETSI MCC |
R4-2009070 |
Void |
ETSI MCC |
R4-2009071 |
Void |
ETSI MCC |
R4-2009072 |
Void |
ETSI MCC |
R4-2009073 |
Void |
ETSI MCC |
R4-2009074 |
Void |
ETSI MCC |
R4-2009075 |
Void |
ETSI MCC |
R4-2009076 |
Void |
ETSI MCC |
R4-2009077 |
Void |
ETSI MCC |
R4-2009078 |
Void |
ETSI MCC |
R4-2009079 |
Void |
ETSI MCC |
R4-2009080 |
Void |
ETSI MCC |
R4-2009081 |
Void |
ETSI MCC |
R4-2009082 |
Void |
ETSI MCC |
R4-2009083 |
Void |
ETSI MCC |
R4-2009084 |
Void |
ETSI MCC |
R4-2009085 |
Void |
ETSI MCC |
R4-2009086 |
Void |
ETSI MCC |
R4-2009087 |
Void |
ETSI MCC |
R4-2009088 |
Void |
ETSI MCC |
R4-2009089 |
Void |
ETSI MCC |
R4-2009181 |
Void |
ETSI MCC |
R4-2009182 |
Void |
ETSI MCC |
R4-2009183 |
Void |
ETSI MCC |
R4-2009184 |
Void |
ETSI MCC |
R4-2009185 |
Void |
ETSI MCC |
R4-2009186 |
Void |
ETSI MCC |
R4-2009187 |
Void |
ETSI MCC |
R4-2009188 |
Void |
ETSI MCC |
R4-2009189 |
Void |
ETSI MCC |
R4-2009190 |
Void |
ETSI MCC |
R4-2009191 |
Void |
ETSI MCC |
R4-2009192 |
Void |
ETSI MCC |
R4-2009193 |
Void |
ETSI MCC |
R4-2009194 |
Void |
ETSI MCC |
R4-2009195 |
Void |
ETSI MCC |
R4-2009196 |
Void |
ETSI MCC |
R4-2009197 |
Void |
ETSI MCC |
R4-2009198 |
Void |
ETSI MCC |
R4-2009199 |
Void |
ETSI MCC |
R4-2009200 |
Void |
ETSI MCC |
R4-2009201 |
Void |
ETSI MCC |
R4-2009202 |
Void |
ETSI MCC |
R4-2009203 |
Void |
ETSI MCC |
R4-2009204 |
Void |
ETSI MCC |
R4-2009205 |
Void |
ETSI MCC |
R4-2009206 |
Void |
ETSI MCC |
R4-2009207 |
Void |
ETSI MCC |
R4-2009208 |
Void |
ETSI MCC |
R4-2009209 |
Void |
ETSI MCC |
R4-2009210 |
Void |
ETSI MCC |
R4-2009211 |
Void |
ETSI MCC |
R4-2009212 |
Void |
ETSI MCC |
R4-2009213 |
Void |
ETSI MCC |
R4-2009214 |
Void |
ETSI MCC |
R4-2009215 |
Void |
ETSI MCC |
R4-2009216 |
Void |
ETSI MCC |
R4-2009217 |
Void |
ETSI MCC |
R4-2009218 |
Void |
ETSI MCC |
R4-2009219 |
Void |
ETSI MCC |
R4-2009220 |
Void |
ETSI MCC |
R4-2009221 |
Void |
ETSI MCC |
R4-2009222 |
Void |
ETSI MCC |
R4-2009223 |
Void |
ETSI MCC |
R4-2009224 |
Void |
ETSI MCC |
R4-2009225 |
Void |
ETSI MCC |
R4-2009226 |
Void |
ETSI MCC |
R4-2009227 |
Void |
ETSI MCC |
R4-2009228 |
Void |
ETSI MCC |
R4-2009229 |
Void |
ETSI MCC |
R4-2009230 |
Void |
ETSI MCC |
R4-2009231 |
Void |
ETSI MCC |
R4-2009232 |
Void |
ETSI MCC |
R4-2009233 |
Void |
ETSI MCC |
R4-2009234 |
Void |
ETSI MCC |
R4-2009235 |
Void |
ETSI MCC |
R4-2009236 |
Void |
ETSI MCC |
R4-2009237 |
Void |
ETSI MCC |
R4-2009238 |
Void |
ETSI MCC |
R4-2009239 |
Void |
ETSI MCC |
R4-2009276 |
Void |
ETSI MCC |
R4-2009277 |
Void |
ETSI MCC |
R4-2009278 |
Void |
ETSI MCC |
R4-2009279 |
Void |
ETSI MCC |
R4-2009280 |
Void |
ETSI MCC |
R4-2009281 |
Void |
ETSI MCC |
R4-2009282 |
Void |
ETSI MCC |
R4-2009283 |
Void |
ETSI MCC |
R4-2009284 |
Void |
ETSI MCC |
R4-2009285 |
Void |
ETSI MCC |
R4-2009286 |
Void |
ETSI MCC |
R4-2009287 |
Void |
ETSI MCC |
R4-2009288 |
Void |
ETSI MCC |
R4-2009289 |
Void |
ETSI MCC |
R4-2009295 |
TR 37.823 |
Ericsson |